platforms usually have a dedicated identifier and a universal identifier of a metadata record, in order to facilitate duplicities check we need to define a universal identifier for resources, so the triple store is able to link statements about this resources from different sources to each other:
The following workflow is suggested:
if a record has a DOI, the DOI is used as universal identifier, prefixed with http://doi.org/
if a resource has no identifier, the filename of the resource is used, with a prefix http://esdac.jrc.ec.europa.eu/content#, a context specific string (namespace) may be required to make sure the identifier is unique
The source platform specific identifier is added in a dedicated metadata section, which indicates one of multiple sources of the record:
If platforms define an identifier for both a catalogue record as well as the resource itself. For now, the suggestion would be to use the catalogue record identifier, else the resource identifier, until this approach appears to be problematic.
platforms usually have a dedicated identifier and a universal identifier of a metadata record, in order to facilitate duplicities check we need to define a universal identifier for resources, so the triple store is able to link statements about this resources from different sources to each other:
The following workflow is suggested:
The source platform specific identifier is added in a dedicated metadata section, which indicates one of multiple sources of the record:
If platforms define an identifier for both a catalogue record as well as the resource itself. For now, the suggestion would be to use the catalogue record identifier, else the resource identifier, until this approach appears to be problematic.