Feature Request - add culture of origin attribute to agents

[Jegelewicz]

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

From interviews about agents with @ekrimmel :

It would be useful if agents could use the culture of origin attribute currently available for catalog objects. Geographical affiliation are important but there is no structured place to capture this on agent records

Describe what you're trying to accomplish
A clear and concise overview of the goals; why are you asking for this?

So there's a doll maker who was born in Kotzebue, and learned this tradition from these doll makers from Kotzebue who have a particular style carving, of making them. But then she lived most of her life in North Pole, right near Fairbanks, and so she's a Inupiaq, and her cultural affiliation is associated with that Inupiaq community of Kotzebue. But she lives in North Pole.

@AJLinn wants to make it clear that this person is associated with that Inupiaq community of Kotzebue.

Describe the solution you'd like
How might we accomplish your goals?

Add an "attribute" to agents that would use the ctculture values.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Create agents for the various cultures and associate agents with them. (This seems like a more powerful and people-centerd approach?)

Additional context
Add any other context or screenshots about the feature request here.

Priority
Please assign a priority-label. Unprioritized issues gets sent into a black hole of despair.

[AJLinn]

It would be important to be able to add multiple cultures here as well (e.g., add lines to attributes, like other fields) for individuals who identify as multi-cultural (e.g., Tlingit / Unangax).

[dustymc]

Possibly could be done as part of #5172, assuming anything survives #6813, and possibly a place to do something clever with #6742

[ewommack]

So that idea would be to have culture of origin as an attribute? Like it is proposed for degree, birth/death dates, etc?

Would it be possible to list more than one culture of origin if it is an attribute?

[Jegelewicz]

Would it be possible to list more than one culture of origin if it is an attribute?

Yes

[dustymc]

Inupiaq community of Kotzebue

Agent attributes aren't built to use code tables, and the request (and the contents of the code table) makes me suspect that's not really what's being asked anyway. I can do this in two ways:

1. Set it up as free text, which will let you say what the person asks you to say. That'll probably be less searchable (Inupiaq community of Kotzebue and Kotzebue Inupiat could both exist and are probably full synonyms), but I think these will be relatively rare "curated" data (I'd expect a few people to enter them for a few people, no random bulkloading with low-information agents) so not sure there's a real problem with that.
2. Set it up using the vocabulary of and referencing the code table, which probably won't quite let you get at those finer distinctions but would be more searchable. I think if we go this way I'd want a subset of the vocabulary: I haven't noticed many 'Prehistoric' folks running around these days, there's no reason to have that option here, these aren't quite the same kind of data needed by catalog records.

@AJLinn thoughts?

[AJLinn]

The Diversity and Inclusion committee believes option 1 is the best here. Free text fields grouped in the Relationships section is our preference.

[dustymc]

Relationships section

Relationships require a related agent, that doesn't seem workable?

I don't think this is an identifier (something meant to uniquely identify an individual, more or less).

Pretty sure it's not a name ("HEY {culture}! ...")

Maybe other (with profile and remarks - probably where any of this info is now).

Otherwise something new?

[AJLinn]

@mkoo is now discussing how this might be better integrated just into the profile paragraph

Identifications, public.

[ewommack]

The Diversity and Inclusion committee can see a need for this attribute to be searchable for agents in a collection or across collections, so support having it added as an Agent Attribute.

[Jegelewicz]

I propose that we close this and create a code table request.

[ewommack]

Issue created: #7476