Settings and activity
34 results found
-
81 votes
Elaine Sloan
supported this idea
·
-
12 votes
An error occurred while saving the comment Elaine Sloan
supported this idea
·
-
73 votesElaine Sloan
supported this idea
·
-
63 votesElaine Sloan
supported this idea
·
-
81 votes
An error occurred while saving the comment Elaine Sloan
commented
This is absolutely critical for consortia, when there are multiple libraries and multiple home pages to manage by different organizations. We are not a centralized consortium, and each library needs to have the permissions to create and manage their own home pages, while still keeping system-level admin with one login.
Elaine Sloan
supported this idea
·
-
31 votes
An error occurred while saving the comment Elaine Sloan
commented
I've had this problem even in the Client, and having this functionality would save me so much time when trying to gather records for batch editing or when using SQL queries to exclude or include certain criteria.
Elaine Sloan
supported this idea
·
-
7 votesElaine Sloan
supported this idea
·
-
42 votesElaine Sloan
supported this idea
·
-
22 votesElaine Sloan
supported this idea
·
-
13 votes
An error occurred while saving the comment Elaine Sloan
commented
This is a critical need for consortia who may have different types of libraries and very spread-out locations. Even though they may share the ILS, they may not have access to all materials for a variety of reasons.
Elaine Sloan
supported this idea
·
-
40 votes
An error occurred while saving the comment Elaine Sloan
commented
The variants of names already entered into the authority record is data that exists, and would be helpful to display and index in Vega. I'm glad to see this proposal as well.
Elaine Sloan
supported this idea
·
-
28 votesElaine Sloan
supported this idea
·
-
47 votesElaine Sloan
supported this idea
·
-
44 votesElaine Sloan
supported this idea
·
The ability to use resource entities in Polaris to integrate econtent records in the catalog and limit views to only those who have access is something that Vega is lacking. Even though there is an API for overdrive, we have resource entities set up for records in our O'Reilly database and we want to keep these in the catalog. Vega currently doesn't provide any way to hide these records, and there is no API integration. Please offer this as a way to hide and separate access for consortia and libraries that want to keep their records in the catalog but also hide them from those who don't have access.