-
Notifications
You must be signed in to change notification settings - Fork 495
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
Document handling of "subject" #1553
Comments
@pdurbin - I fixed the display issue someone had improperly edited the table markdown causing it to not be recognized by Sphinx or GitHub https://github.com/IQSS/dataverse/blob/master/doc/sphinx-guides/source/api/sword.rst The documentation for how we handle dcterms:subject is in the crosswalk table and can be sent to QA |
@posixeleni thanks for making this change. closing ticket as this is now found in the crosswalk table. |
Actually, more importantly (I believe), the example XML shows how you can use controlled vocabulary values in dcterms:subject now:
|
@pdurbin both help 👍 |
Looking into #1430 revealed that behavior with regard to
dcterms:subject
in SWORD has changed from 3.6 to 4.0. In 3.6 this field mapped tokeyword
. Now it maps to bothkeyword
andsubject
with special processing if the value matches the controlled vocabulary. This should be documented.The text was updated successfully, but these errors were encountered: