-
Notifications
You must be signed in to change notification settings - Fork 147
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
Feature/add creator support #302
Conversation
- Introduced creator fields (URI, name, email, URL, type, identifier) alongside publisher fields. - Updated the RDF graph serialization to include creator details. - Extended existing tests to validate the creator functionality. - Applied similar fallback logic for creator as used for publisher.
…add-creator-support
…add-creator-support
40a9ba3
to
253b552
Compare
387d0d3
to
f7da907
Compare
@amercader Do you have time to review this one? Thanks in advance! |
Thanks for this @hcvdwerf , I have many open fronts but will get to this eventually! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @hcvdwerf , forgot to push the green button on these comments. Just some minor things and we are good to go
("notes", DCT.description), | ||
("url", DCAT.landingPage), | ||
("version", OWL.versionInfo), | ||
("title", DCT.title), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't include formatting changes like these ones
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
help_text: Entity responsible for making the dataset available. | ||
|
||
- field_name: creator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
creator
was not part of the recommended properties in DCAT AP 2 so let's keep it just in the full schema.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
examples/ckan/dataset.json
Outdated
"title": ""}] | ||
"creator": { | ||
"name": "John Doe", | ||
"mbox": "johndoe@example.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be "email" as per the definition in the schema files, and the publisher above is wrong too. mbox was used in a really ancient parser no longer supported
"mbox": "johndoe@example.com" | |
"email": "johndoe@example.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
examples/ckan/temp
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this is not needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
- Added fields to store creator details (name, email, URL, and identifier) in the DCAT profile. - Implemented functionality to serialize and deserialize creator information similar to the publisher. - Updated RDF generation logic to include creator fields in the output graph. - Enhanced unit tests to verify proper handling and serialization of creator metadata.
d045430
to
d8461e2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@amercader Thank you for your comments, @amercader! I’ve made adjustments to the code based on your feedback.
help_text: Entity responsible for making the dataset available. | ||
|
||
- field_name: creator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
("notes", DCT.description), | ||
("url", DCAT.landingPage), | ||
("version", OWL.versionInfo), | ||
("title", DCT.title), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
examples/ckan/dataset.json
Outdated
"title": ""}] | ||
"creator": { | ||
"name": "John Doe", | ||
"mbox": "johndoe@example.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
examples/ckan/temp
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check
Thanks @hcvdwerf , nice one |
Add Creator Support to DCAT Extension
This PR introduces functionality for managing and displaying creator information in datasets, aligning with the DCAT vocabulary. Key additions include:
Creator Fields: Similar to the publisher, we now support creator metadata fields:
creator_name
: The name of the dataset creator.creator_email
: The creator's email address.creator_url
: The homepage or URL related to the creator.creator_identifier
: A unique identifier for the creator, such as an ORCID or other URI.RDF Serialization/Deserialization:
Unit Tests:
This enhancement aligns with the ongoing efforts to ensure full support for the DCAT-AP 2/3 profiles in CKAN's DCAT extension and improves metadata expressiveness by adding proper attribution for dataset creators.