Settings and activity
31 results found
-
8 votes
Alexis Schaffer
supported this idea
·
-
6 votesAlexis Schaffer
supported this idea
·
-
5 votes
An error occurred while saving the comment Alexis Schaffer
supported this idea
·
-
20 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
·
-
26 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
·
-
58 votesAlexis Schaffer
supported this idea
·
-
52 votesAlexis Schaffer
supported this idea
·
-
55 votesAlexis Schaffer
supported this idea
·
-
69 votesAlexis Schaffer
supported this idea
·
-
16 votesAlexis Schaffer
supported this idea
·
-
91 votesAlexis Schaffer
supported this idea
·
-
102 votesAlexis Schaffer
supported this idea
·
-
134 votesAlexis Schaffer
supported this idea
·
-
16 votesAlexis Schaffer
supported this idea
·
An error occurred while saving the comment Alexis Schaffer
commented
Adding this would bring parity with the client - currently if you import in the client, a 020$z does NOT match and overwrite an existing bib with a 020$a or another 020$z that has the same ISBN. We have taken advantage of this by having 020$z IBSNs listed for the individual items in a kit, without risking overwrites if there is a new import of one of the individual titles. But an IBSN search will still bring up the kit because it contains that title.
-
20 votesAlexis Schaffer
supported this idea
·
-
9 votesAlexis Schaffer
supported this idea
·
-
48 votesAlexis Schaffer
supported this idea
·
-
54 votesAlexis Schaffer
supported this idea
·
-
44 votesAlexis Schaffer
supported this idea
·
-
35 votesAlexis Schaffer
supported this idea
·
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.