-
Notifications
You must be signed in to change notification settings - Fork 0
Copy number doesn't display #21
Comments
JIRA User: Chris Delis (cedelis) Can you provide example bib? Thanks. |
JIRA User: Jessica Gibson (gibsonjc) Copy numbers as found in Voyager Item records are displaying now as: Copy c. The word "Copy" and the "c." are redundant and only one is necessary. Would it be possible to remove the "c." from displaying? Current production catalogs have the word "Copy:" Example can be seen in any record that has an Item Record, but here is an example where I added an additional copy 63: |
JIRA User: Jessica Gibson (gibsonjc) When there isn't an item to get a number from, the word Copy still appears by itself, which is a bit untidy. |
JIRA User: Chris Delis (cedelis) I discovered where the c. comes from: In VXWS, the following config file, e.g., MILdb/tomcat/vxws/context/vxws/ui/eng/vxws.properties: holdings.item.copynumber.label=c. If I set it to blank, i.e., holdings.item.copynumber.label= the label will disappear. I plan to do this soon, but not at the moment, as I'm working a different issue. Just wanted to point it out. |
JIRA User: Chris Delis (cedelis) I've made this change to VXWS. |
Resolved: 2016-04-12 10:37 AM |
JIRA issue created by: Jessica Gibson (gibsonjc)
Originally opened: 2016-01-13 12:35 PM
Traditionally, we have used the copy number from the MFHD 852$t for our OPAC displays; however, given that out-of-the-box VuFind2 isn't displaying much, if any, information from the MFHD as far as I can tell, I can understand why it isn't doing that!
But VuFind2 does display a lot of things from the Voyager Item record, and it has the word "Copy" hardcoded somewhere in its display, it just doesn't seem to be pulling the copy information from the Item record, or it is getting the information but not showing it.
(I don't know if this is a specific problem to solve or if it will be solved another way by ultimately making more information from the MFHDs display instead, but I thought it was unusual and worth noting.)
The text was updated successfully, but these errors were encountered: