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

Link METS Metadata with Notice's named-graphs #550

Open
cristianvasquez opened this issue Oct 17, 2024 · 0 comments
Open

Link METS Metadata with Notice's named-graphs #550

cristianvasquez opened this issue Oct 17, 2024 · 0 comments

Comments

@cristianvasquez
Copy link

Currenly this is how we establish a connection between the METS metadata and the corresponding Notices.

Each Notice in RDF contains a Notice Publication Number, represented as follows:

<epo:hasNoticePublicationNumber>00191514-2024</epo:hasNoticePublicationNumber>

In the METS package, this Notice Publication Number is referenced using the following elements:

<cdm:work_id_document rdf:datatype="http://www.w3.org/2001/XMLSchema#string">ted:2024_S_65_00191514</cdm:work_id_document>
<cdm:work_id_document rdf:datatype="http://www.w3.org/2001/XMLSchema#string">oj:JOS_2024_65_R_00191514</cdm:work_id_document>
<cdm:procurement_public_number_document_in_official-journal rdf:datatype="http://www.w3.org/2001/XMLSchema#string">00191514</cdm:procurement_public_number_document_in_official-journal>
<cdm:procurement_public_number_edition rdf:datatype="http://www.w3.org/2001/XMLSchema#positiveInteger">202465</cdm:procurement_public_number_edition>

While it is technically possible to link the metadata to the Notice using query manipulation, this method is suboptimal.

Instead, it's recommended to establish these links by using a named graph.

@cristianvasquez cristianvasquez changed the title Link METS Metadata with RDF Notices using Named-Graphs Link METS Metadata with Notice's named-graphs Oct 17, 2024
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

1 participant