Feature #11081

Add new occupation access point with notes field to authority records, supported by Actor occupations taxonomy

Added by Dan Gillean over 3 years ago. Updated about 3 years ago.

Status:VerifiedStart date:04/12/2017
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Actor
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

Overview:
This feature will introduce a new way to capture and search/browse information about actors. A new taxonomy for "Actor occupations" will be added to AtoM (empty by default), and a custom, repeatable set of fields with an autocomplete linked to the Actor occupations taxonomy and a notes field per access point will be added to actor view and edit pages. We will also make sure that these new fields are supported via import and export (EAC-CPF XML and CSV), and that users can make use of the new data via search and browse, with the addition of the occupation data to the search index, and a new Occupations facet added to the authority record browse page.

Features covered by this enhancement include:
  • Adding a new "Actor occupations" taxonomy
  • Creating a new access points area in the Authority record view and edit templates
  • Adding repeatable occupation fields (term, note) to the Authority record edit and view pages
  • Adding new Occupation data to the Elasticsearch index for actors
  • Adding a new Occupations facet on the Authority record browse page, which will use the Actor occupation terms added as access points
  • Ensuring that CSV and EAC-CPF XML import and export capture Actor occupation data
Notes:
  • As usual, ensure that all user interface labels and content fields are i18n wrapped so they can be translated, and that aria tags are added where appropriate.
  • There will be a database schema migration needed for upgrading users

For the EAC-CPF XML work, we will make use of the following elements:

For the CSV import and export, the following names can be used:

  • actorOccupations
  • actorOccupationNotes

These fields should support piped inputs so that multiple values can be imported and exported - and it should be possible to have an occupation term without a corresponding descriptive note. In the archival description CSV templates it is possible to manage event/actor data by using a literal NULL value in paired columns you want to leave empty - I believe this started around issue #8844, but see the docs here for context. We should do the same here, so it is possible to have the following:

-----------------------------------------------------------------------------
|        actorOccupations           |         actorOccupationNotes          |
=============================================================================
| ocuppation 1|occupation 2         |  NULL|Note for occupation 2           |
-----------------------------------------------------------------------------

History

#7 Updated by Dan Gillean over 3 years ago

  • Target version changed from Release 2.4.0 to Release 2.5.0

#8 Updated by José Raddaoui Marín over 3 years ago

  • Target version changed from Release 2.5.0 to Release 2.4.0
  • Estimated time deleted (32.00)

#9 Updated by José Raddaoui Marín over 3 years ago

  • Status changed from New to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

Merged in 67f0e48

#10 Updated by Dan Gillean over 3 years ago

  • Status changed from QA/Review to Verified

#11 Updated by Dan Gillean about 3 years ago

  • Assignee deleted (Dan Gillean)
  • Requires documentation deleted (Yes)

Also available in: Atom PDF