Facet Updates for Topic: Revisit Q1 2023

[orangewolf]

User Story:
ARCE would like to be able to separate Topic facet up into different facets, as there is currently too much under one category for that to be useful. UCLA cannot update the OAI feed with new metadata, so SSS has advised that a shortcut to this would be to utilize the Notes fields for three new Topic attributes. We'll then create new facets based on the new attributes.

Indexing Sheet updated with attributes: https://docs.google.com/spreadsheets/d/1m9kaT0dn_cwYQdPiHz4gTVDaQYtZoyw7ILHoHLi3MPg/edit#gid=0

Attribute names will be:

• Fieldwork Activity
• Object/Monument Type

We'd expect something like:

<mods:note type="new_facet_one">Pharaohs; Upper-Egypt; Art, Ancient--Egypt</mods:note>
<mods:note type="new_facet_two">Mosques; Facades; Iwans</mods:note>
<mods:note type="new_facet_three">Ritual in art; Personnel; Priests--Egypt; Deities</mods:note>

We cannot do all three facets in one notes field. Each facet must be in its own note.

Acceptance:

• ARCE to Define names of attributes to create in Notes from Topics ("Fieldwork Activity" and "Object/Monument Type")
• UCLA to add columns for new Note.attribute(s)
• New Note.attribute(s) are in feed
• Create facets mapped to new Note.attribute(s)

Notes from Dawn:

Here’s a bit more information about how we handle the Notes field that might help. UCLA has set up its ingest script to take any Note.[attribute] column and turn it into a new string field. We want to approve all new attribute cases to make sure there isn’t an existing field that will do the trick and to make sure it’s an attribute that fits with our longer-term plans, but it does allow us some flexibility in adding new fields without having to rescript our ingest process. So, if I add a column named Notes.cats, then a new field named Note.cats should show up in the feed once that data is ingested. Notes is the only field that we can do this with, so we wouldn’t do it for Genre because that would involve us having to update our ingest script/service (and I don’t think we'd want to break Genre up into sub fields anyway).

For these new fields, we would just be adding two additional Note.attribute fields that ARCE would use when putting their metadata together. These will be string fields for us, not facetable, so the only work I think Notch8 would need to do is to take the values present in those two “Note." fields and treat them as facets on the ARCE frontend. So, yes, this is the quick fix that requires no coding on UCLA’s part, but allows ARCE to publish that metadata.

[crisr15]

Lea Ann:
Waiting on Client to get new notes field in the OAI feed