Andy (UCLA)
My feedback
17 results found
-
33 votesAndy (UCLA) supported this idea ·
-
24 votesAndy (UCLA) supported this idea ·
-
46 votesAndy (UCLA) supported this idea ·
-
17 votes
An error occurred while saving the comment Andy (UCLA) supported this idea · -
43 votes
An error occurred while saving the comment Andy (UCLA) commentedI absolutely agree with this idea, and was surprised to learn this problem exists. Example in our catalog:
https://search.library.ucla.edu/permalink/01UCS_LAL/1763hao/alma9997032535706533The underlying MARC record has correctly linked 700/880 fields, with $6 showing the relation between each pair of fields. That relation should be preserved in the public display.
I've added screenshots with the correct MARC display and the incorrect Primo VE display.Andy (UCLA) supported this idea · -
75 votes
An error occurred while saving the comment Andy (UCLA) commentedIn addition to the reasons others have already listed, add sharing holdings data with others. Currently in Alma, we have to work around this by embedding specific holdings fields in bib records and publishing these, then either manipulating the output or expecting our partners to pull the holdings data out of these hybrid records.
Alma APIs are an option for small data sets, but not suitable for projects involving tens or hundreds of thousands of records.
Please allow us to export our holdings data in the standard MARC format.
Andy (UCLA) supported this idea · -
74 votesAndy (UCLA) supported this idea ·
-
17 votesAndy (UCLA) supported this idea ·
-
300 votesAndy (UCLA) supported this idea ·
-
8 votesAndy (UCLA) shared this idea ·
-
135 votesAndy (UCLA) supported this idea ·
-
1 voteAndy (UCLA) shared this idea ·
-
103 votesAndy (UCLA) supported this idea ·
-
4 votesAndy (UCLA) shared this idea ·
-
56 votesAndy (UCLA) supported this idea ·
-
110 votesAndy (UCLA) supported this idea ·
-
19 votesAndy (UCLA) supported this idea ·
An error occurred while saving the comment Andy (UCLA) commentedI agree. The data for number of records, start/stop times for jobs, who submitted the job - it's all visible in the Alma UI and can be retrieved from "Monitor Jobs -> History" for as long as the job reports are retained.
Please add this data to Analytics, instead of requiring a manual review of each job to get the data which is not included in the "Monitor Jobs -> History" Excel export, like number of records processed.
Thanks --Andy / UC Los Angeles
I 100% agree with this. Storage is cheap (even at Alma's scale), and the MARC record doesn't have an infinite number of fields or subfields. Being able to report on the full extent of data in our MARC records is important. Normalization rules in Alma are helpful, but there are times when we need to explore data in ways which Alma itself does not (and probably should not) support. Analytics is that tool.