Settings and activity
40 results found
-
25 votes
Lloyd Chittenden
supported this idea
·
-
15 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
13 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
10 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
10 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
11 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
14 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
18 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
8 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
31 votes
This will be implemented in Sierra in 2027.
An error occurred while saving the comment
Lloyd Chittenden
supported this idea
·
-
23 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment
Lloyd Chittenden
commented
This should also include all authorized fields, 6xx, 8xx, anything else I may have forgotten.
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.
-
19 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
shared this idea
·
-
7 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
shared this idea
·
-
50 votes
The product team will review this idea for consideration for a future release.
Lloyd Chittenden
supported this idea
·
-
39 votes
The product team will review this idea for consideration for a future release.
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
·
-
20 votes
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
·
-
21 votes
Lloyd Chittenden
supported this idea
·
-
23 votes
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
·
-
19 votes
Lloyd Chittenden
supported this idea
·
Lack of action on this definitely leaves me with the impression that they plan on Sierra EOL well before 2038.