Date: Fri, 29 Mar 2024 10:35:01 +0100 (CET) Message-ID: <756885055.3223.1711704901111@confluencesrv1.awi.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3222_1231667568.1711704901110" ------=_Part_3222_1231667568.1711704901110 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You're in the right place if you want to offer metadata for <= strong>searching in the portal. If you want to provide data products for the portal viewer = with our spatial data infrastructure, look here.
To become a content provider for the portal you have to provide metadata= for your datasets, articles or map projects. We basically support the defa= cto standardized OAI-PMH and the OGC CSW me= tadata harvesting interfaces. One of these standards should be accessible f= rom the internet via HTTPS without authentication. If you have no catalog a= nd standardized interfaces to your content until now, you might have a look= at the GeoNetwork solution. Different metadata schemata a= nd profiles are supported, e.g. ISO19115, but also customiz= ed ones. For special cases, also other web-resources can be harvested, but = are not preferred.
Checkpoints for basic metadata
Checkpoints for extended metadata profiles
:information: You provide basic metadata and support standard interfaces= ? Fine. Read about = Harvesting and Indexing.
We are using an internal JSON metadata format (schema, example) fo= r harmonized indexing and full-text search against an El= asticsearch cluster. Metadata is harvested regulary once a night from c= onfigured content providers. Metadata is annotated, e.g. with information f= rom Gazetteers to resolve geographical locations to place names, during har= vesting. So users are able to search also for places names not only for geo= metries.
As content provider you have to map your metadata content against the gi= ven JSON Schema. Best you are using international vocabularies for your m= etadata content. For example
:information: The list of vocabularies is not fixed and can be easily ex= panded. But you really should map wherever possible to achieve harmonizatio= n.
:information: There is a harvesting and indexing sandbox where you can test your mappings, harvesting and = search. Please contact o2a-support@awi.de to g= et access.
:information: To finally become a content provider contact o2a-suppo= rt@awi.de.