search

sul-dlss / exhibits

Stanford University Libraries online exhibits showcase
https://exhibits.stanford.edu
Other
19 stars 7 forks source link

Generate a separate field for each value of /mods/name/role in an exhibit #546

Open caaster opened 7 years ago

caaster commented 7 years ago

Story: Metadata often includes agents with significantly different roles in relation to the object (for example, interviewer vs. interviewee, or author vs. donor). Exhibit curators would like to distinguish names associated with the object by their associated roles for display and faceting in order to provide this important information to the user, and also to suppress certain roles from displaying if desired.

Acceptance criteria:

  1. A separate display field should be available for each value of /mods/name/role/roleTerm[@type=”text”] appearing in the exhibit metadata, labeled with that value. The display field should contain the value of the <namePart> element enclosed in the same <name> element as the <roleTerm>.
  2. A separate facet field should be available for each value of /mods/name/role/roleTerm[@type=”text”] appearing in the exhibit metadata, labeled with that value. The facet should include the value of the <namePart> element enclosed in the same <name> element as the <roleTerm>.
  3. If multiple <roleTerm type=”text> elements appear within the same <name> element, the associated <namePart> value should appear in each role field.
  4. If a /mods/name element appears in the exhibit metadata that does not contain a <roleTerm type=”text”> element but does contain a <roleTerm type=”code” authority=”marcrelator”> element, the value of that element should be mapped to the corresponding role term in the MARC Code List for Relators, and that term treated in the same way as a <roleTerm type=”text”> value.
  5. If a /mods/name element appears in the exhibit metadata that does not contain a <roleTerm type=”text”> element or a <roleTerm type=”code” authority=”marcrelator”> element, the role “Other contributor” should be supplied and treated in the same way as a <roleTerm type=”text”> value.

Fixture objects are in #889, and 1-5 apply

arcadiafalcone commented 7 years ago

It looks like markdown is dropping words in angle brackets (mostly before the word "element", as well as at the end of #1 and #2). Using the <insert code> formatting will prevent that.

arcadiafalcone commented 6 years ago

See also #936. Requirements in this ticket should be adjusted for consistency with that display.