TPAC: Use in-db unapi for copy display in record summary

[Dan Scott]

* Evergreen master

Evergreen currently uses in-db unAPI calls to display bib record and copy data in search results, yet uses a complex JSON query to retrieve bib and copy data for the detailed record display.

By adding the required attributes (such as due_date, age_protect, and copy and call number IDs) to the in-db unAPI functions, we can harmonize access to bib and copy data in TPAC and focus future changes on in-db unAPI rather than maintaining parallel access methods.

I have pushed a branch with the recommended changes to the working repo at user/dbs/in-db-unapi-circ-due-date

[Dan Scott (denials)]

Force-pushed a clean rebase against master into the user/dbs/in-db-unapi-circ-due-date working branch, now that the non-fixed-width set of commits has been merged.

[Dan Scott (denials)]

The unapi database function portion of the code has been merged by Mike Rylander into remotes/working/collab/miker/unapi2_subobject_improvement, but we now need to update the TPAC to pass the new hstore values for callnumber / copy paging as that functionality is currently broken.

(Quick thought: create unapi function wrappers that just do the right thing for paging if given limit / offset INT arguments instead of hstore?)

[Dan Scott (denials)]

Rather than creating wrapper functions, I pushed a quick TPAC fix into Mike's collab branch that simply sets the paging limit at acp=>5 to unbreak TPAC.

[Dan Scott (denials)]

Removed "pullrequest" tag from this bug as the unapi support needs to evolve further to support all of the functionality that the json_query in the record details page currently provides.

[Jason Stephenson (jstephenson)]

or, should this one just not be targeted at a milestone for now?