Option to define another set of records to be included in the Database search
The database search in Primo includes only electronic collections with collection type “database” or electronic collections with a collection level URL and an unsuppressed bibliographic record.
Even though you can change the electronic material type of a portfolio to “database” these titles can’t be searched through the database search. This means we have to add local database collections even though the title can be activated through the community zone.
An example is the electronic collection “De Gruyter Databases”. I should like to be able to include these in the database search.
Anne Skov
shared this idea
-
Anonymous
commented
It was possible to add portfolios to the database search in Primo BO but no longer when we switched to VE. We had to change a number of portfolios into local databases. In some cases this should have been done anyway (we emptied our "Miscellaneous ebooks/journals collections) but in others it was a nuissance.
-
Lauren Gibbs
commented
This would be very helpful for us as well. We recently needed to make all of our Springshare A-Z database list databases discoverable in Primo. Some of these are portfolios in Alma, so we had to add local collections to make them discoverable as databases. This complicates the management of these resources and duplicates our work. We had to add a ton of notes and link POLs so we could trace the local collection back to the actual portfolio that containes the cost, renewal, and access settings. Being able to designate a portfolio as a database so it is discoverable as a database would solve this issue for us.