Summary: | MARCItemFieldsToOrder should allow use of items table field names | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Acquisitions | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | gmcharlt, matt.blenkinsop |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Andrew Fuerste-Henry
2020-08-04 12:37:57 UTC
I'm renaming this bug and redirecting it a bit. All of the values one can map in MARCItemFieldsToOrder directly correspond to database fields, but a few of them use names that differ slightly from those fields. This has been an ongoing source of confusion. Can we make MARCItemFieldsToOrder work with *either* the current order object names *or* the database field names? The syspref wants: nonpublic_note, public_note, loc, and copyno The items table names those: itemnotes_nonpublic, itemnotes, location, and copynumber All other potential values listed in the syspref description match their corresponding database fields. Currently on main, either "loc" or "location" work when enter in MARCItemFieldsToOrder, but itemnotes, itemnotes_nonpublic, and copynumber do not work. |