Settings and activity
50 results found
-
8 votes
An error occurred while saving the comment 
Lloyd Chittenden
supported this idea
·
An error occurred while saving the comment Lloyd Chittenden
commented
Even if you were using linked data, you probably don't want to look at this in your records all the time. It should hide away, and maybe have a rollover popup, or something to let you see it if you want to.
Also include subfield |0, not just |1.
-
5 votesLloyd Chittenden
shared this idea
·
-
2 votesLloyd Chittenden
shared this idea
·
-
17 votesLloyd Chittenden
supported this idea
·
-
13 votesLloyd Chittenden
supported this idea
·
-
14 votes
An error occurred while saving the comment Lloyd Chittenden
commented
We are a consortium with a very similar problem. Our members have different requesting policies on things, particularly DVDs. Some of them don't allow holds and others do. If one of the non-holdable libraries gets the first copy, then it will shut down requests on that title for the whole system until another library gets a copy, regardless of the fact that there are order records from libraries that do allow holds, and want people to be able to put on holds.
We have implemented a very clunky work around. This suggestion would be a huge improvement.
Lloyd Chittenden
supported this idea
·
-
6 votesLloyd Chittenden
shared this idea
·
-
13 votesLloyd Chittenden
supported this idea
·
-
28 votes
An error occurred while saving the comment Lloyd Chittenden
commented
I don't know anything about this at all, but it sounds like an important best practice.
Lloyd Chittenden
supported this idea
·
-
4 votesLloyd Chittenden
supported this idea
·
-
17 votesLloyd Chittenden
supported this idea
·
-
13 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 Lloyd Chittenden
commented
For our consortia, we probably can't let members have SQL access without being able to limit information by scopes and account units. So this would be useful to us.
Lloyd Chittenden
supported this idea
·
-
29 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Lloyd Chittenden
supported this idea
·
-
9 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
Lloyd Chittenden
supported this idea
·
-
11 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
An error occurred while saving the comment Lloyd Chittenden
commented
This should be an option. Sometimes you might prefer not to have the subfields, but sometimes it is critical. For example, when you export 020, you can't tell whether it is |a or |z, which is a huge difference.
Lloyd Chittenden
supported this idea
·
-
33 votes
This idea has been selected to include in Sierra 6.4
Lloyd Chittenden
supported this idea
·
-
31 votes
This idea was selected in MEEP voting for inclusion in Sierra 6.3.
Lloyd Chittenden
supported this idea
·
-
38 votes
This idea was selected in MEEP voting for inclusion in Sierra 6.3.
Lloyd Chittenden
supported this idea
·
-
23 votes
This idea was selected in MEEP voting for inclusion in Sierra 6.3.
Lloyd Chittenden
supported this idea
·
An error occurred while saving the comment Lloyd Chittenden
commented
This would be fine, but jarcache can get screwed up every time you start SDA. There really should be a more comprehensive solution, like checking the number of files with every start.
-
31 votesLloyd Chittenden
supported this idea
·
An error occurred while saving the comment Lloyd Chittenden
commented
I'd still want the option of copying to a review file.
This should also include all authorized fields, 6xx, 8xx, anything else I may have forgotten.