Allow Customizable Picklist Scoping Based on Database Hierarchy

[JDAM2k4]

Requested by Jordi from the Museu de Ciències Naturals de Barcelona via email.

We would like fields that depend on Collection Object tables to have collection-specific values, while tables that depend on Discipline (such as Locality, Collecting Event, Loan, etc.) and Division (such as Accession and Agent) should always be shared across collections.

Picklists are primarily customizable at the Collection level. This can be tedious if multiple collections use the same picklist with little to no changes, as it requires the institution to have multiple picklists with identical names to support multiple collections. This could be resolved by adding the ability to customize the scope of each individual pick list by using a "Scope pick list to current collection" checkbox, for instance.