The MODS exporter serializes all subject terms as <mods:topic>, rather than conditionally based on their term type as the MARC exporter does. For example, a subject term that is classified in ArchivesSpace as type 'Geographic' should export as <mods:geographic>, but instead exports as <mods:topic>.
Environment
None
Activity
Show:
Adam JazairiMarch 8, 2018 at 5:58 PM
Thanks for your work on this, Lora! Just updated our dev instance to 2.3.1 and it's working great.
Lora WoodfordFebruary 22, 2018 at 5:57 PM
In working through this I realized there was nothing built in to handle the possibility of a single subject encompassing multiple subject terms and term types (e.g. "African Americans – Education, Higher – Maryland" or something of that sort). I have added in logic that joins the subject terms together with " – " as is done elsewhere in the applications, and have selected the first subject term type as the basis for the mods tag. This may be open to further discussion, but at least, for now, the exporter is able to handle instances in which subjects include multiple subdivisions with several terms and term types.
I used the same logic as is present in the MARC21 model to map the ArchivesSpace subject term types to MODS subject types, but could use eyes that know MODS better than I.
The MODS exporter serializes all subject terms as <mods:topic>, rather than conditionally based on their term type as the MARC exporter does. For example, a subject term that is classified in ArchivesSpace as type 'Geographic' should export as <mods:geographic>, but instead exports as <mods:topic>.