ILLiad Ideas
7 results found
-
Update z39.50 search fields and "ILLiad citation" when article/loan info is updated and saved
When citations are fixed or changed on the ILLiad request, the z39.50 search fields and "ILLiad citation" section are not also updated, but remain the same as when the request was opened. It would be helpful if those fields were also updated when citation changes are saved, so information does not also need to be manually added to search fields, and so the proper citation can be referenced from the z39.50 page.
1 vote -
Improve Z39.50 and FOLIO connection
There's already a call out to FOLIO to improve how multi-volume holdings appear in XML to make them visible via Z39.50, but it would probably help matters if Atlas Systems and FOLIO worked together to make this improvement for all libraries migrating to FOLIO. https://issues.folio.org/browse/ZF-84
Basically, if there are multiple volumes of a title, only summary holdings and inaccurate availability status are visible through Z39.50. Some libraries have implemented custom addons to get around this, but this is really a workaround to what should be a standard function.
7 votes -
Support for WMS WorldShare Management Services Z39.50
OCLC's WMS system credentials can exceed ILLiad's current username/password field lengths. Field sizes need to be expanded to support OCLC authentication for WMS Z39.50.
2 votes -
Add additional Result Mapping options for Z39.50
It would be nice if there were one or two more fields where data grabbed via Z39.50 could be imported into ILLiad. In particular, "Item Num" would be an ideal place to hold a barcode, rather than having to concatenate it to a different value (as described here: https://support.atlas-sys.com/hc/en-us/community/posts/360006750353-Finding-Importing-the-Barcode-Field).
6 votes -
Improve retrieval of Alma holdings when there are multiple volumes.
ALMA doesn't have holdings for each volume when there are multiple volumes, so in z39.50 only the most recent volume is pulled up in the search. Is there a way for ILLiad to handle this better? If not within z39.50, then via an addon maybe? (This is from ticket 8080)
22 votes -
Allow Z39.50 searches to work with servers that don't support unicode
Several Z39.50 servers don't support Unicode or non-ASCII characters. If the ILLiad title has those characters in it, the search returns no results. It may be necessary to replace characters with their Latin equivalent before searching.
5 votes -
Have a custom key that allows Sites to choose if the characters \/;:,.&? get stripped off or not
Some characters may get dropped from Title when displayed in the Title Search box. This affects the Search results. For example, when testing Angels & Demons, the book did not show until the ampersand was added back in.
0 votes
- Don't see your idea?