Settings and activity
64 results found
-
9 votes
Kimberly Allen
supported this idea
·
-
13 votes
An error occurred while saving the comment Kimberly Allen
supported this idea
·
-
12 votes
An error occurred while saving the comment Kimberly Allen
commented
A variety of reasons can cause a branch to close (and sometimes quite quickly.) This enables the admin to quickly and accurately update the holdings availability for each branch. This provides better service to the patrons.
Kimberly Allen
supported this idea
·
-
54 votes
Please note that an AUDIENCE Facet already exists in Vega and can be turned on in the staff admin.
An error occurred while saving the comment Kimberly Allen
commented
We don't use Vega, but our consortial discovery layer provides filters by genre. Per our Reference folks, patrons find it extremely helpful in narrowing their searches. We have a graphic novel collection and one of my current projects is to enhance those with the generic graphic novel heading with addition fields of Nonfiction comics, Historical comics, Shojo manga, etc. as appropriate.
Kimberly Allen
supported this idea
·
-
82 votes
This idea has been selected to include in Sierra 6.4.
An error occurred while saving the comment Kimberly Allen
commented
FYI: as written up on the roadmap, libraries WILL be allowed to specify the yearly date. https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/856-automate-moving-ytdcirc-to-lyrcirc-at-year-end-and-don-t-update-last-updated-date
Kimberly Allen
supported this idea
·
An error occurred while saving the comment Kimberly Allen
commented
I'll join in with a YES for the automatic update and not changing the last updated date.
And as noted by others, the date chosen should be determined by the library. -
20 votesKimberly Allen
supported this idea
·
-
8 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment Kimberly Allen
commented
From a bibliographic standpoint: we're an academic library with a vast range of materials and various customizations in our records. I'm with Jeremy in that I prefer we gen reports for staff to review. What may be an error to the AI, may be legit local practice.
-
7 votesKimberly Allen
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Kimberly Allen
supported this idea
·
-
6 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Kimberly Allen
supported this idea
·
-
7 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Kimberly Allen
supported this idea
·
-
12 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Kimberly Allen
supported this idea
·
-
15 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment Kimberly Allen
commented
As noted, this makes the catalog more accurate which provides better customer service and limits the errors staff have to track down.
Kimberly Allen
supported this idea
·
-
25 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Kimberly Allen
supported this idea
·
-
12 votesKimberly Allen
supported this idea
·
-
28 votes
An error occurred while saving the comment Kimberly Allen
commented
I don't play in this area, but this would be essential information for folks who do.
Kimberly Allen
supported this idea
·
-
9 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Kimberly Allen
supported this idea
·
-
4 votesKimberly Allen
supported this idea
·
An error occurred while saving the comment Kimberly Allen
commented
We have deep and complex serial holdings where volume info and copy number are critical. This is a big time saver.
-
37 votes
An error occurred while saving the comment Kimberly Allen
commented
We have now had more experience with this. It appears that large data loads can trigger a java process spike with the keyword indexing/Lucene searcher and indexer. III saw out of memory errors and increased the memory of the searcher and indexer. However, we continue to see issues corresponding to large loads. Now our admin monitors "slow request" warnings in sierradb:/iiidb/errlog/lucenes-app.log. He opens a ticket when they become excessive. III then restarts the keyword indexing/Lucene engine.
An error occurred while saving the comment Kimberly Allen
commented
We've hit this more than once. In those cases catalogers discovered it by happenstance. We really need an alert! So that we can quickly debug and resolve it.
Kimberly Allen
supported this idea
·
-
16 votesKimberly Allen
supported this idea
·
We are almost always sitting at the limit. Staff turnover also adds to the difficulty in determining ownership. Being able to see initials and last date and time would be a huge help. The ability to rename would be another win. What may seem like a descriptive name to the original owner may be a mystery to others.