Settings and activity
40 results found
-
24 votes
Daniel Messer
supported this idea
·
-
10 votesDaniel Messer
supported this idea
·
-
80 votes
An error occurred while saving the comment Daniel Messer
supported this idea
·
Daniel Messer
shared this idea
·
-
24 votesDaniel Messer
shared this idea
·
-
11 votesDaniel Messer
shared this idea
·
-
66 votesDaniel Messer
supported this idea
·
An error occurred while saving the comment Daniel Messer
commented
In Polaris Leap 7.7, you cannot use Leap to import a list of bibliographic record IDs into a bibliographic record set. The import feature only accepts ISBNs. While I understand why ISBNs might be an option for an import criteria, they shouldn't be the only option.
* A bibliographic record need not have an ISBN. And if it does not have an ISBN, it can't be imported at all using this feature.
* An ISBN might be shared by other bibliographic records, which means that those other bib records might show up in the record set, even if the operator doesn't want them to.
* The bibliographic control number is meant to be a clear and unique identifier for an individual bibliographic record, which is exactly why it should be the primary criteria for a bibliographic record import.
Someone using this ISBN import feature could accidentally and unknowingly pull in bibliographic records they do not want to alter or delete. This could lead to data pollution or, even worse, data loss. When I discovered this feature, I was working with a library that has over 1,600 bibliographic records that share ISBNs. As things go, I'll be discouraging library staff from using this feature or, at the very least, double-checking everything they add to a record set using this feature.
Please add bibliographic record ID to the import criteria for bibliographic record sets and make it the default option for data importing.
-
24 votesDaniel Messer
shared this idea
·
-
22 votes
An error occurred while saving the comment Daniel Messer
commented
Please keep SimplyReports updated in any way possible. It's an important piece of the Polaris stack that needs bugfixes and updates.
Daniel Messer
supported this idea
·
-
15 votes
An error occurred while saving the comment Daniel Messer
commented
I fully support this, if for no other reason than the PolarisTransactions database needs to be expanded to track this and many other events.
Daniel Messer
supported this idea
·
-
42 votesDaniel Messer
supported this idea
·
-
20 votesDaniel Messer
supported this idea
·
-
31 votesDaniel Messer
supported this idea
·
-
31 votesDaniel Messer
supported this idea
·
-
13 votesDaniel Messer
supported this idea
·
-
12 votesDaniel Messer
supported this idea
·
-
33 votesUNDER REVIEW · 0 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Daniel Messer
supported this idea
·
-
29 votesUNDER REVIEW · 1 comment · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →Daniel Messer
supported this idea
·
-
11 votesDaniel Messer
supported this idea
·
-
7 votesDaniel Messer
supported this idea
·
-
19 votesDaniel Messer
shared this idea
·
For those in the chat here, the .xls file is actually a tab delimited file (TDF). If you rename it with that .tdf extension? You should be able to open it without too much fuss from Excel.