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

controlled_access_terms content types as taxonomies #912

Closed
seth-shaw-unlv opened this issue Aug 29, 2018 · 3 comments
Closed

controlled_access_terms content types as taxonomies #912

seth-shaw-unlv opened this issue Aug 29, 2018 · 3 comments
Assignees

Comments

@seth-shaw-unlv
Copy link
Contributor

seth-shaw-unlv commented Aug 29, 2018

Based on our conversation yesterday related to #896 we decided I would explore turning the Islandora-CLAW/controlled_access_terms content models (People, Corporate Bodies, Families, Geographic Locations, and Subjects) into taxonomies; because they are means of organizing content, not necessarily content themselves.

Tagging: @rtilla1 @rosiel @dannylamb

@seth-shaw-unlv seth-shaw-unlv self-assigned this Aug 29, 2018
@seth-shaw-unlv
Copy link
Contributor Author

Based on a conversation with @rosiel in IRC:

  • Preferred name will no longer be required.
  • We are dropping auto_entitylabel (although we will point people to it in case they want it). This may result in double-entry (but that is, in many cases, desirable; especially for migrations).

@rosiel
Copy link
Member

rosiel commented Aug 29, 2018

The idea is that the "Name" of the taxonomy term (the built-in pseudo-field thing, equivalent to the "Title" of a node) will be a free-text place to enter the Agent's name string as desired. This way it will not be tied to a specific formatting of structured name elements, which prevents us from locking in a single cultural model of "names".

[Edit: and allows you to incorporate disambiguation information as needed, such as dates. And allows you to use values from LC's Name Authority File.

But also, the Preferred Name, a https://www.drupal.org/project/name field, will be available if you do want to represent some names as structured. Whether you implement something akin to auto_entitylabel to avoid the requirement for double-entry will be up to you.]

@dannylamb
Copy link
Contributor

Resolved via Islandora/controlled_access_terms@66bab1a

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