5. 55
Authority bestanden
Lokale authoritybestanden opgeladen vanuit Aleph naar Alma en
nieuwe aangemaakt (namen, titels, TWO, UDC, Chinese
headings)
Alma geconfigureerd voor het aanmaken van nieuwe en het
onderhouden van bestaande authority records
=> De mogelijkheid van lokale authority bestanden biedt ook
meerdere mogelijkheden voor het onderhoud en delen van
lokale onderwerpsontsluiting.
Workshop op dinsdag 29 november 2016!
9. 99
Werkgroepen
3 Vergaderingen van de volledige werkgroep : Vooral gericht op nieuwe
functionaliteit en inventarisatie en oplossen van knelpunten
2 workshops:
Periodiekenbeheer en werken met sets
Beheer E-bronnen
Deelwerkgroep statistieken : uitwerking van acquisitiestatistieken voor AA
Krachtlijn voor volgend jaar : onderzoeken of Alma acquisition niet voor meer
instellingen opportuun kan zijn, eventueel in combinatie met hun ERP.
Acquisitie
10. 1010
Werkgroepen
Elk semester een vergadering + vergaderingen van de sub-werkgroepen:
Statistieken en rapportering: er werd al heel wat aangepast in Analytics
Documentatie: de handleiding is helemaal nagekeken en wordt zeer binnenkort online
gezet
Workshop: opfrissing FF opleiding
Highlights 2016
Rappels worden gebundeld
Aanpassing aanvraag/reservatie formulier in Limo
Aanpassing IBL-formulier in Limo
Dit alles moet aangevraagd worden via de Helpdesk
Fulfillment
11. 1111
Werkgroepen
3 vergaderingen van de volledige werkgroep
Evaluatie documentatie en bijkomende noden/verwachtingen
Rapporten en statistieken vanuit Alma RM
Nieuwe en aangepaste functionaliteit
3 workshops:
Gebruik van de Repository Search en toelichting van aantal nieuwe functies en aangepaste functionaliteit
Basisopleiding E-bronnen in Alma
Authority records in Alma en in LIBISnet (29.11)
1 vergadering subwerkgroep inhoudelijke ontsluiting
evaluatie huidige situatie en rondvraag over wat er nodig/wenselijk is
Focus 2017: optimalisering documentatie, focus op consistent metadabeheer (o.m. op basis van authority
functionaliteit)
Resource Management
12. 1212
Planning 2017
Alma UX
Alma Digital
Optimalisatie data
Linked data en enrichment
Werkgroepen
Rapporten en statistieken
Verhogen betrokkenheid
Conversies
MIM
EBS?
...
Integraties
SAP - Alma terugkoppeling (KU Leuven)
13. 1313
Alma Digital
Uitrol van Alma Digital.
Enerzijds de mogelijkheid bieden aan eindgebruikers om een
digitaliseringsaanvraag te plaatsen in Limo en deze op te volgen en af
te werken vanuit Alma.
Geïnteresseerden?
Anderzijds de mogelijkheid aanbieden aan partnersinstellingen om
gedigitaliseerd materiaal te beschrijven in Alma en te bewaren in de
Alma cloud omgeving
16. 1616
Idea exchange
Extend the "interested users" functionality
Acquisition librarians want to extend the current "interested users" functionality in
order to serve the end user in a better and faster way. The current "interested
users" functionality is not sufficient enough, to become useful and really benefit
from this functionality we would like to extend it with:
• The ability to sort the interested user list.
Use case: some users (e.g. academic staff) have priority and should get the issue
first!
• Make it possible to create hold requests on these items regardless of the existing
fulfillment policy:
Use case: some libraries don't allow requests for available items, but this means
they're not able to request items for interested users during receiving. (Apparently
in the beginning of going live with Alma this was possible...).
• Make it possible to automatically loan the issue to the first interested user when
receiving! This way limited routing functionality is made possible for (print) journal
subscriptions.
Acquisitions
17. 1717
Idea exchange
Add "item policy" and "temporary location" automatically to predicted
issues
Acquisition librarians want to add automatically the "item policy" and
"temporary location" to predicted issues to speed up their work and limit the
number of clicks. At this moment the added value of prediction pattern
functionality is being restricted by the lack of functionality (parameter setting)
…
Use case: It’s not possible to add the item policy/temporary location as a
parameter to continuous pol’s. If issues are created via prediction patterns
the item policy/temporary location should be indicated automatically based
upon parameter settings on pol level. This would save a lot of time and
additional clicks when receiving the issues.
In addition this should also be possible when items are created based upon
templates via the “receive new items” button.
Acquisitions
18. 1818
Idea exchange
Opening hours of the library in Alma and renewing in Primo
Circulation desk librarians want to make a distinction between library opening hours
in Alma and service hours in Primo so users can still renew items on loan in Primo
that day after closing time of the library.
Some libraries close at 5 PM. The due hours of the items loaned in these libraries
are thus 5 PM. But in fact the student should be able to renew his items until the
end of the day, which is 11:59 PM in Primo.
We have also configured that for students there is a patron limit of max overdue =
0. Which means that there is a block on the student record from the moment he has
1 item overdue.
When the student has items due on 05/11 - 5 PM and he is logged into Primo at
5:05 PM he can no longer renew his items because of this block.
So make it possible to have a distinction between the library opening hours in Alma
and the Primo service hours, or create the possibility that the grace day takes this
into account so that the items still can be renewed until the end of the day.
Fulfillment
19. 1919
Idea exchange
Change the “No requesting from available holding” functionality (check
item availability)
Circulation desk librarians want to make a distinction between items and
holdings that are (not) available for requesting purposes.
Patrons shouldn't be able to request items that are available, but they should
be able to request items that are NOT available. In our case our items are
created under the same holding, and Alma checks the holding for availability,
not the item.
Use case: 1 holding with 3 items (with the same item description): 2 items
are loanable, 1 item should stay in the shelves for consulting.
When the 2 loanable items are on loan and the 3rd one being a non-loanable
copy, the first 2 items cannot be requested, there’s no request button.
We want to be able to show a request button when an item is on loan, even
though there is still a no loan item available under the same holding.
Fulfillment
20. 2020
Idea exchange
“Pushing” sets of records from an Institution Zone to the Network Zone (consortial
environment)
In some cases (actually quite regularly) we are facing the following problem in our Alma Network
configuration. Using a normalization rule, we want to make bulk changes to a set of bibliographic
records (stored in the Network Zone) where this set can only be built in the Institution Zone because
the query uses search criteria from either localized fields in the bibliographic record or from the
inventory (holdings, items, portfolio, …). Building the query and saving the set in the IZ is obviously
not a problem but running normalization rules on NZ bibliographic records from within an IZ is. Non-
localized fields in the NZ bib records cannot be changed from within an IZ.
Therefore we would appreciate the development of a functionality which would allow to ‘export’ or
‘push’ sets from an IZ to the related NZ where we could then apply the necessary normalization on
the bib records. At the moment we use an elaborate workaround exporting IZ sets as XML and
extracting the NZ MMS ID of each of the records to a csv-file which can be used to build a new set in
the NZ. This is particularly troublesome if we have to ‘gather’ NZ bib records based on similar
queries in our thirty odd IZ’. We have to repeat the XML-export/MMS ID extraction for each IZ.
Considering the fact that the NZ MMS ID is already available in each of the bib records in the IZ’s, it
might not be too complicated to develop a job which would build a ‘mirror’ NZ set based on an IZ set
of bib records (so an all/physical/electronic/digital titles set).
Resource Management
21. 2121
Idea exchange
Make it possible to delete a NZ bib record from the Institution tab
for records that are CZ in origin (consortial environment)
It is possible to delete a Network Zone bib record from one's institution
tab, provided that (1) it is a record created within the Network Zone and
(2) it is not "Held by" other institution from the network. However, when
the record is originally from the Community Zone deleting it is not
possible. Even when it is not "Held by" any other institution from the
network. This results in a multitude of Community Zone bib records to
which there are no holdings in the network. Needless to say, it will be a
great asset if institutions can actually delete them.
Electronic Resources
22. 2222
Idea exchange
Make it possible to add new individual titles/portfolios to a
contributed collection (for which one has the ownership)
Current functionality for contributing an electronic collection to the CZ is
a one-time action. Missing here is the functionality that the owner of
this contributed collections can update it, i.e. adding new individual
titles/portfolios.
Electronic Resources