config.yml updates - meta

[kspurgin]

The idea here is to update the config.yml for every record type in each existing converter profile (core, anthro, etc) to ensure:

• the file is using the current format to specify authority and vocabulary records the converter can create if they don't exist
• each field populated by a vocabulary or authority is configured (as well as each authority for the field if multiple authorities can be used as sources)

The purpose is to support the ability to get reports on all vocabulary/authority terms for which records do not exist used in data during migrations and other projects. The resulting vocabulary/authority terms may or may not be transferred to CSpace, but the ability to review them is helpful.

We discussed how to do this elsewhere, so I won't write more here except to outline the approach I suggested:

• do the core config first
• copy the authorities/vocabularies section for each core record type to other profiles' configs because the configs do not inherit from core
• delete any config for fields not included in the non-core profile
• add/revise any config for fields added or overridden by the non-core profile

To test, you will import a csv that contains in the specified fields values that do not already exist in the specified authority or vocabulary. The tool should create records for the authority or vocabulary and give you the option to transfer them. The interface for this is not great yet, but I'd like to improve it.

An example may clarify: If you import a batch of collectionobjects and one has ownerPerson column = 'Lisa Tim', and 'Lisa Tim' is not in Person authority already... then, after a successful import, if you click the Transfer button at the top, select your batch, you should see both CollectionObject and Person under Type.

[kspurgin]

@Paulmulonzia - if you have general questions re: the config.yml update work, please ask them on this issue, so all that info can be found together.