...

• Generate qa_all_fields_#_#.csv

  • This flags new fields in new? column and adds the dumbfieldname useful for pivot table checks

• Generate qa_deleted_fields_#_#.csv

  • This should be nothing but headers unless fields were supposed to be deleted

• Generate qa_changed_fields_#_#.csv

  • This will include the full row from the previous version all fields CSV and the current/under QA all fields CSV if any data in the row has changed

  • Go through this carefully to verify all changes are expected/intentional

• Generate qa_nonunique_field_names.csv

  • This reports duplicate field names within the same record type. These will work if the fields have different xpaths, but can be confusing in CSV templates and discussions with clients.

  • Look for any with status = new and suggest less confusing name.

• Checks for duplicate field paths (name and xpath the same)

  • These will not work and need to be fixed!

  • (Currently the check will run. None like this exist. If any are found you will need to implement code to generate appropriate output)

• Checks for fields with xml_path (i.e. xpath) depth greater than 4.

  • Deeper xpath nesting is not technically a problem for the CollectionSpace application, but deeper data structures are going to require additional work in the cspace-config-untangler and collectionspace-mapper.

Inconsistency/pattern check

...

• Check for typos in field names, labels, and xml_path

• Check for xml_path values more than 4 segments long.

  This is not technically a problem for the CollectionSpace application, but you are going to have a headache updating the Untangler to untangle deeper data structures, and the collectionspace-mapper to create the proper XML

  that ui_info_group, ui_path, and ui_field_label are being extracted correctly

  • If any are not, this might indicate issues with messages for fields. Or you may need to tweak code in the cspace-config-untangler to fix the ui label extract. Problems with this are often related to form field info not matching up with field definition info because the ns_for_id isn’t getting set correctly.

Generate and validate record mappers from new configs

...