Security, dependencies, requirements

What's Changed

• Dependencies and requirements by @kspurgin in #80
• bump nokogiri version due to security advisory by @kspurgin in #81

Full Changelog: v1.9.5...v1.9.6

Less fiddly config; better support for community mappers

Merge pull request #79 from collectionspace/bundler-security-warning

bump versions (triggered by bundler version security alert)

Version-specific column naming

Profile versions associated with 6.1 or earlier will use the previous "fancy" column naming algorithm. Starting with 7.0, all will use the "consistent" column naming algorithm.

I had previously just changed the code to emit the consistent column names, but that was going to be a problem for generating correct templates/mappers for anyone who hasn't upgraded to 7.0.

This PR adds the ability to switch between column naming algorithm used, based on the profile version. This logic is in the LAST_FANCY_VERSION constant of the CCU::ColumnNameStylable mixin module.

Column name changes; Generate dev mappers

• Use consistent column name format for columns for authority terms to: FieldnameAuthoritytypeAuthoritysubtype
• Add ability to generate dev mappers

Add core nonhierarchicalrelationship mapper to dev manifest

Adds core nonhierarchicalrelationship mapper to dev manifest so that the special behavior of this relationship can be tested in collectionspace-csv-importer without downloading all mappers

Mappers and templates for release 7.0

Adds mappers, templates, comparison files, and mapper manifest for release 7.0 versions of all community profiles

Mapper manifests

• now stored in data/mapper_manifests
• one manifest with mappers for all current versions of community profiles, and one smaller dev manifest have been added
• instructions on how to generate mappers and mapper manifests have been added in doc

Removes reliance on cspace-services API

The cspace-services REST API was used only for grabbing the list of vocabularies (Term Lists) defined for an instance.

With CollectionSpace 6.1, we no longer need to do this in order to get the data source information for each field.

If you are working with older versions of CollectionSpace, you may need to use an older release.

Change details: #66

Output mediaFileURI to media templates

See #63

Ignore new record type created for ad-hoc reporting

Export record type should be ignored by the Untangler. Now it is.