CDC #464 - VIAF Identifiers

[dleadbetter]

This pull request fixes an issue with the ViafIdentifierForm using an outdated payload structure. It also fixes a CSS issue with the width of the search input element.

This pull request will remain a draft until a new release of core_data_connector is published.

[blms]

Is it ns1 for every result in the response? I actually had to configure a Python VIAF API library to use the new API response and I found that it increased ns2, ns3 etc per each subsequent result. Though not 100% sure we're using the same endpoint (this one was for /search I believe). And since we're only doing this after selecting an entry maybe we only want the first result?

Just in case, here are all the changes I had to make in that library:

API reference

• Changes to the search params and headers:

  • maximumRecords can only be a maximum of 10 (documented)
  • sortKeys has been renamed to sortKey, and only accepts holdingscount (documented)
  • httpAccept/Accept params no longer work, but passing an Accept header does (not documented)

• Changes to search results (none documented):

  • Search results are now nested as records: { record: [] } or records: { record: {} }
  • Metadata is now nested under VIAFCluster inside of recordData
  • Most JSON keys are now "namespaced" using ns2:, ns3:, ns4: prefixes, which increase per result. For example, a result's recordData might look like

    {"ns2:VIAFCluster": {"ns2:mainHeadings": {"ns2:data": {"ns2:text": "My Name"}}}}

    and the following search result will have the same keys but with ns3: prefixed, etc. up to ns11.
  • Other small things, like numberOfRecords count being nested under content now, and @about renamed to about