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

Document handling of "subject" #1553

Closed
pdurbin opened this issue Mar 2, 2015 · 5 comments
Closed

Document handling of "subject" #1553

pdurbin opened this issue Mar 2, 2015 · 5 comments

Comments

@pdurbin
Copy link
Member

pdurbin commented Mar 2, 2015

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 to keyword. Now it maps to both keyword and subject with special processing if the value matches the controlled vocabulary. This should be documented.

@pdurbin pdurbin added this to the Documentation - 4.0 milestone Mar 2, 2015
pdurbin added a commit that referenced this issue Mar 2, 2015
Discovered editing metadata via SWORD isn't working. Opened #1554

The new behavior for subject/keyword is not documented. Opened #1553
@pdurbin pdurbin reopened this Jun 2, 2015
@posixeleni
Copy link
Contributor

@pdurbin I had documented this new mappin behavior in the DC Terms - Dataverse DB Element Crosswalk in the SWORD API documentation see #1077 but for some reason this table is no longer showing in the guide. Who removed this?

posixeleni pushed a commit that referenced this issue Jun 2, 2015
@posixeleni
Copy link
Contributor

@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 pushed a commit that referenced this issue Jun 2, 2015
@eaquigley
Copy link
Contributor

@posixeleni thanks for making this change. closing ticket as this is now found in the crosswalk table.

@pdurbin
Copy link
Member Author

pdurbin commented Jun 2, 2015

Actually, more importantly (I believe), the example XML shows how you can use controlled vocabulary values in dcterms:subject now:

   <!-- Dataverse controlled vocabulary subject term -->
   <dcterms:subject>Chemistry</dcterms:subject>
   <!-- keywords -->
   <dcterms:subject>coffee</dcterms:subject>

@posixeleni
Copy link
Contributor

@pdurbin both help 👍

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

3 participants