Settings and activity
46 results found
-
34 votes
Alexis Schaffer
supported this idea
·
-
76 votesAlexis Schaffer
supported this idea
·
-
15 votes
An error occurred while saving the comment Alexis Schaffer
supported this idea
·
-
23 votesAlexis Schaffer
supported this idea
·
-
15 votes
An error occurred while saving the comment Alexis Schaffer
commented
Yes, this is very frustrating, especially if it's large record set. If you're adding or removing records piecemeal as you find the ones you need, having to reload the record set after every change is very annoying.
Alexis Schaffer
supported this idea
·
-
21 votes
An error occurred while saving the comment Alexis Schaffer
commented
Yes, the whole point of sorting is to better see ALL the records grouped in whatever way you sorted. If you're only sorting what appears on the first page, it's not an accurate reflection of what's in the record set.
Alexis Schaffer
supported this idea
·
-
10 votes
An error occurred while saving the comment Alexis Schaffer
commented
While you can directly edit the 006, 007, and 008, they do not automatically overwrite like it does in the client. Because they are fixed fields with a standardized number of characters, it would be easier for experienced cataloguers to just type what needs to be there, rather than deleting the correct number of characters or opening the workform.
Alexis Schaffer
supported this idea
·
-
14 votes
An error occurred while saving the comment Alexis Schaffer
commented
Would love this feature! Since formats/TOMs are currently hierarchical and may have multiple ways to create them (eg in the 006, the 007, the LDR, the 008 or a combo of all of these), it's not always easy to tell if you made the correct change, or made all the changes you need to get the format you want. It would be much easier to tell if the fix is working if you could see the change in format right in the bib, rather than opening a duplicate check or going back to refreshed search results.
Alexis Schaffer
supported this idea
·
-
7 votes
An error occurred while saving the comment Alexis Schaffer
commented
It's always annoyed me in the client that this info wasn't available from the search results, like it is with bib and item records. Adding a column for record set ID would reduce clicks and be much appreciated!
Alexis Schaffer
supported this idea
·
-
10 votes
An error occurred while saving the comment Alexis Schaffer
commented
Yes, currently if I have a big record set and want to filter by year, I might still get results where a number is in the title or author dates. Filtering by column would (I assume) allow multiple filters as well, if you need to narrow even more, such as by date and material type or whatnot.
Alexis Schaffer
supported this idea
·
-
24 votesAlexis Schaffer
supported this idea
·
-
15 votes
An error occurred while saving the comment Alexis Schaffer
commented
Needed for client parity. This would help with narrowing search results when trying to clean up records that have the same TOM, but are used in different ways, such as graphic novels or other special materials that are all books, but have special item material types.
Alexis Schaffer
supported this idea
·
-
7 votes
An error occurred while saving the comment Alexis Schaffer
commented
A history of notifications/errors would also be helpful in tracking how frequently an issue is occurring, when, and to what user. Also helpful to re-find the message if it fades too quickly to write it down or get a screenshot, especially if you aren't expecting something to go wrong.
Alexis Schaffer
supported this idea
·
-
11 votesAlexis Schaffer
supported this idea
·
-
12 votesAlexis Schaffer
supported this idea
·
-
24 votesAlexis Schaffer
supported this idea
·
-
16 votesAlexis Schaffer
supported this idea
·
-
11 votes
An error occurred while saving the comment Alexis Schaffer
commented
Personally I think the main bib should be locked if you are editing it in the compare tool. That being said, it is nice to be able to go back and see item details in the bib, which are not available in the compare tool. But maybe the bib could still be locked for editing if you have the compare tool open? Likewise, I think if you've made edits in the bib and go to open the compare tool, there should be a pop-up telling you to save, or indicating that the changes made won't show up in the compare unless you save first.
Alexis Schaffer
supported this idea
·
-
21 votes
An error occurred while saving the comment Alexis Schaffer
commented
This would be an excellent addition. As others have said, sometimes an incoming record won't be as complete as an existing record and will overwrite the additional work our cataloguers have done to further enhance the record. While there are currently rules to reject incoming records based on encoding level, it's not always an accurate measure of the record. Our own database is not as clean as it could be either, so a better record might still be encoded as a lower level because it was missed in copy cataloguing or because the cataloguer forgot to adjust it. Being able to review potential duplicates (with specific criteria) before loading would be a helpful option to have.
Alexis Schaffer
supported this idea
·
-
30 votes
An error occurred while saving the comment Alexis Schaffer
commented
This is especially important for libraries that have multilingual collections - for languages that have special characters that aren't easily input by keyboard, or that you need to install multiple keyboard options to use and then memorize the shortcuts for. If you need French, that's fairly straightforward, but as soon as you add Swedish or Indigenous languages like Dene, you start having a whole bunch of special characters that aren't in the "English-international" keyboard set. Having a diacritics/special characters box in LEAP would be very helpful.
Alexis Schaffer
supported this idea
·
I've also encountered this issue, specifically with SQL searches where there are multiple conditions (such as local fields or specific subfields) that aren't accessible with the regular search.