Skip to content
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

Mapping of ISO metadata datestamp to DCAT #124

Open
uvoges opened this issue May 28, 2024 · 4 comments
Open

Mapping of ISO metadata datestamp to DCAT #124

uvoges opened this issue May 28, 2024 · 4 comments

Comments

@uvoges
Copy link

uvoges commented May 28, 2024

Generally the DCAT-AP metadata only contains information about the data itself not the metadata. That means that the date from the gmd:dateStamp attribute is not mapped to DCAT-AP as it is about the metadata not the data. This mapping is important as the metadata datestamp is important for harvesting purposes.This should be clarified in GeoDCAT-AP

@jakubklimek
Copy link
Contributor

Actually, this is mapped to DCAT-AP's dcat:CatalogRecord, specifically dcterms:modified, as can be seen in this example and these lines of the XSLT.

@uvoges
Copy link
Author

uvoges commented May 29, 2024

Jakub, Do you think 2 datestamps are needed the one of the original metadata item which is being mapped and of the actual DCAT Catalog Record entry?
...taking into account different harvesting scenarios...?

@jakubklimek
Copy link
Contributor

Well, the original metadata item is represented by the DCAT Catalog Record - so they should be the same thing. Do you have another opinion?

@uvoges
Copy link
Author

uvoges commented Jun 26, 2024

No, would be fine with me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants