Changes between Version 5 and Version 6 of proposals/InspireDownloadServiceAsAtom


Ignore:
Timestamp:
Jun 6, 2013, 2:03:22 AM (11 years ago)
Author:
pvgenuchten
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • proposals/InspireDownloadServiceAsAtom

    v5 v6  
    44|| '''Date''' || 2012/09/18 ||
    55|| '''Contact(s)''' || Paul van Genuchten ||
    6 || '''Last edited''' || ||
     6|| '''Last edited''' || 2013/06/06 ||
    77|| '''Status''' || OnGoing ||
    8 || '''Assigned to release''' || 2.x ||
     8|| '''Assigned to release''' || 2.12 ||
    99|| '''Resources''' || ||
    1010|| '''Ticket #''' || ||
     
    4242
    4343{{{
     44<OpenSearchDescription>
     45        <ShortName>[AtomServiceFeed:feed.title]</ShortName>
     46        <Description>[AtomServiceFeed:feed.title]</Description>
     47        <!--URL of this document-->
     48        <Url type="application/OpenSearchDescription+xml" rel="self" template="http://nationaalgeoregister.nl/opensearch/[ServiceMetadata:fileIdentifier]/OpenSearchDescription.xml"/>
     49        <!--Generic URL template for browser integration-->
     50        <Url type="application/atom+xml" rel="results" template="http://nationaalgeoregister.nl/opensearch/[ServiceMetadata:fileIdentifier]/search?q={searchTerms}"/>
     51
     52<!-- repeat for each Atom dataset feed -->
     53<!--Describe Spatial Data Set Operation request URL template to be used
     54        in order to retrieve the Description of Spatial Object Types in a Spatial
     55        Dataset-->
     56        <Url type="application/atom+xml" rel="describedby" template="http://nationaalgeoregister.nl/opensearch/[ServiceMetadata:fileIdentifier]/search?spatial_dataset_identifier_code={inspire_dls:spatial_dataset_identifier_code?}&amp;spatial_dataset_identifier_namespace={inspire_dls:spatial_dataset_identifier_namespace?}&amp;language={language?}&amp;q={searchTerms?}"/>
     57
     58<!-- repeat step for each attached dataset -->
     59        <!--Get Spatial Data Set Operation request URL template to be used in
     60        order to retrieve a Spatial Dataset-->
     61        <!-- For download of GML files, use this template. -->
     62        <Url type="application/gml+xml;version=3.2" rel="results" template="http://nationaalgeoregister.nl/opensearch/[ServiceMetadata:fileIdentifier]/search?spatial_dataset_identifier_code={inspire_dls:spatial_dataset_identifier_code?}&amp;spatial_dataset_identifier_namespace={inspire_dls:spatial_dataset_identifier_namespace?}&amp;crs={inspire_dls:crs?}&amp;language={language?}&amp;q={searchTerms?}"/>
     63        <!-- format differentiation. If multiple formats are supported (for the same CRS), return an Atom feed containing multiple links. In that case use results="application/atom+xml" for multiple downloadable files. -->
     64        <Url type="application/atom+xml" rel="results" template="http://nationaalgeoregister.nl/opensearch/[ServiceMetadata:fileIdentifier]/search?spatial_dataset_identifier_code={inspire_dls:spatial_dataset_identifier_code?}&amp;spatial_dataset_identifier_namespace={inspire_dls:spatial_dataset_identifier_namespace?}&amp;crs={inspire_dls:crs?}&amp;language={language?}&amp;q={searchTerms?}"/>
     65<!-- Voor elke Service Feed de contactgegevens -->
     66        <Contact>[AtomServiceFeed:author.name]</Contact>
     67        <Tags>[ServiceMetadata.Keywords]</Tags>
     68        <LongName>[AtomServiceFeed:feed.subtitle]</LongName>
     69
     70<!-- repeat for each dataset dataset and crs  -->
     71        <Query role="example" inspire_dls:spatial_dataset_identifier_namespace="[AtomServiceFeed:feed.entry.inspire_dls:spatial_dataset_identifier_namespace]" inspire_dls:spatial_dataset_identifier_code="[AtomServiceFeed:feed.entry.inspire_dls:spatial_dataset_identifier_code]" inspire_dls:crs="[AtomDatasetFeed:feed.entry.category@term]" language="[AtomDatasetFeed:feed.entry.link[rel=”alternate”]@xml:lang]" title="[AtomDatasetFeed:feed.entry.title]" count="1"/>
     72
     73<!-- per Atom Service feed / Service metadata record combination: -->
     74        <Developer>[AtomServiceFeed:author.name]</Developer>
     75        <!--Languages supported by the service. The first language is the default language-->
     76        <Language>[AtomServiceFeed:feed.title@xml:lang]</Language>
     77
     78}}}
     79
     80{{{
    4481/geonetwork/srv/dut/rss.search?any=
    4582}}}
     
    4885/geonetwork/srv/eng/rss.detail?uuid={uuid}&lang={lang}
    4986}}}
    50 This is also an implementation of the "Describe Spatial Data Set"-operation
     87This could also become an implementation of the "Describe Spatial Data Set"-operation, however note that this operation uses dataset-identifier/namespace and not metadata identifier
    5188
    5289GN will return a document like:
     
    91128            <updated>2012-06-18T15:35:04Z</updated>
    92129        <!-- Optioneel: een samenvatting / omschrijving  -->
    93                 <summary>Download de dataset Geografische namen (DEMO) NamedPlaces, via deze feed</summary>
     130                <summary>Download the dataset Geografische namen (DEMO) NamedPlaces, via this feed</summary>
    94131        <!-- The service feed contains the boundingbox, in polygon format -->
    95132        <georss:polygon>50.7539 3.37087 50.7539 7.21097 53.4658 7.21097 53.4658 3.37087 50.7539 3.37087</georss:polygon>
     
    104141
    105142
    106 == Implementation with harvested ATOM will require functionality like this ==
     143== Implementation with harvested ATOM will require additional functionality ==
    107144
    108145'''Collect ATOM'''
     146
    109147In the situation that the data provider provides its own Atom document, geonetwork should not link to the Atom document generated by the catalogue, but to the document provided by the data provider.
    110148To be able to include the ATOM contents in the Lucene index, we'll need to harvest the Atom document on regular intervals.
     
    112150
    113151'''Harvest ATOM'''
     152
    114153A usecase to consider is that we also create an ATOM harvester which will be able to harvest iso19115 and iso19119 metadata from Atom feeds.
    115154
    116155'''Validate Atom'''
     156
    117157Before being able to collect or harvest Atom Feeds I guess we'll need Atom XSD in GN
    118158
     
    130170Also if GN finds such an atom feed url in the gmd:url field, the metadata record-view could get the feed contents and return the linked datasets inside the Atom document and present them as hyperlinks
    131171
    132 
    133 '''TODO:'''
    134  
    135  * create Atom output format (new rss.detail endpoint using custom xslt)
    136  * Add option to iso19115 'online resource' section to auto generate a hyperlink to an Atom feed referring to the uploaded dataset
    137  * Add option to harvest iso19115/iso19119 metadata from an Atom Feed
    138  * If online resource section contains atom link, present as human readable in metadata record view
    139  * filter by iso19119-uuid
    140  * filter by "inspire compliency"?
    141  * Complience testing
     172''' Link to Inspire thesaurus '''
     173
     174A reference should be made from the ATOM feed to a SKOS/RDF thesaurus on the JRC website (http://inspire-registry.jrc.ec.europa.eu/registers/FCD). This thesaurus has a format currently not supported by geonetwork (each term is in a separate web location, the central document only has a list of links/identifiers). We might be able to support the format if with an upgrade of Sesame. Else we should transform the thesaurus to a readable format. A user should at least include a single keyword from this thesaurus in each record, that dhouls have an Aton document generated by geonetwork. Most probably in a new version of the discovery service specification a link to this thesaurus will be required anyway.
     175
     176'''Other challenges when generating Inpire compliant Atom documents'''
     177
     178* The Atom feed should have some indication of filesize of the download, we might be able to find this info with a java function (if the file resides on the geonetwork server). This kind of info can also be filled in iso19115 ( transfersize), but it seems a total of all files attached to the record.
     179* multilingual support, how to register the language of the external resource (proposal: gmd:online@xlink:role)
     180* projection (crs) of the download, geonetwork doesn't have "epsg:xxxx" in rs_identifier, and crs seems to be registered for all gmd_online
     181
    142182
    143183=== Proposal Type ===