Skip to content

DCAT-us writer: identifier #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hmaier-fws opened this issue Sep 1, 2023 · 0 comments
Open

DCAT-us writer: identifier #265

hmaier-fws opened this issue Sep 1, 2023 · 0 comments
Assignees
Labels
discussion Issue for discussion by stakeholder group writer:dcat-us Data.gov DCAT-US Schema

Comments

@hmaier-fws
Copy link

Issue

Determine mapping to use when writing mdJSON to the required DCAT-US identifier field. The field is defined as:

Description:
A unique identifier for the dataset or API as maintained within an Agency catalog or database.

Usage Notes:
This field allows third parties to maintain a consistent record for datasets even if title or URLs are updated. Agencies may integrate an existing system for maintaining unique identifiers. Each identifier must be unique across the agency’s catalog and remain fixed. It is highly recommended that a URI (preferably an HTTP URL) be used to provide a globally unique identifier. Identifier URLs should be designed and maintained to persist indefinitely regardless of whether the URL of the resource itself changes.

Initial proposal is to use the following rules:

  • IF resourceInfo.citation.identifier.namespace = "DOI"
  • SELECT resourceInfo.citation.onlineResource.uri

ELSE

  • if "DOI" within resourceInfo.citation.onlineResource.uri
  • SELECT resourceInfo.citation.onlineResource.uri

Related issues: #251, #264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Issue for discussion by stakeholder group writer:dcat-us Data.gov DCAT-US Schema
Projects
None yet
Development

No branches or pull requests

3 participants