Versions Compared

Old Version 2

changes.mady.by.user Kara Young

Saved on

compared with

New Version Current

changes.mady.by.user Kara Young

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Library Team - Corinne Wolfson, Alessandra Seiter, Julie Petzold, and Carol Kentner

LTS Lead - Kara Young

Overview of Project

  • Transition from ARES
  • Transition to Leganto
    • Make sure HKS classes are in Canvas
  • High volume (11-13,000 digitized course materials a year)
  • Primarily journal articles, chapters, etc
  • Concerns:
    • Copyright clearance
    • Manage rights- Access rights adjustments (will need many different access rights policies)
    • Usage limited only to Leganto/Course users (not HOLLIS users)
    • Need to add stub bib records for materials not in Alma
    • Workflow requirements - time intensive
  • Timeline:
    • Pilot for fall- make recommendation by end of summer
    • Next meeting end of June

Tasklist

Completed DateTaskSystemPhaseWho
Planning

Library submits project request.Alma Support CenterPlanningLibrary

LTS/Library will meet to review request and verify project meets pilot criteria.ZoomPlanningLibrary/LTS

LTS will create wiki page for project that tracks all mapping information, timelines, and decision points and share with the stakeholders.EmailPlanningLTS

Library will provide configuration information for the service in the project request ticket.Alma Support CenterPlanning

Library


Library will provide Alma login forms for staff who will create/update Alma recordsAlma Support CenterPlanningLibrary
Testing & Implementation

Update Alma sandbox loginsAlmaTestingLTS

Update Alma sandbox configuration

  • Create collection
  • Create Access policy
AlmaTestingLTS
Not Applicable

Configure NextCloud for project

  • coming soon
NextCloudTestingLTS

Alma sandbox: load records / digital objectsAlmaTesting

Library


HOLLIS sandbox: request records be published from AlmaAlmaTesting

Library


HOLLIS sandbox: confirm records/functionalityHOLLISTestingLibrary

Request configuration changes, if needed, and LTS pre-production reviewAlma/HOLLISTestingLibrary

Update Alma production loginsAlmaMove to productionLTS

Update Alma production configuration

  • Create collection
  • Create Access policy
AlmaMove to productionLTS

Update Alma wiki documentation for Alma-D

WikiMove to productionLTS

Update local workflow documentationVariesMove to productionLibrary
Post

Announce ServiceEmailCommunicationLibrary

Create dashboards/canned reports Alma AnalyticsAlmaService ReviewLibrary/LTS

Evaluate service/determine next stepsAlmaService ReviewLibrary/LTS

Library Service Information

ParameterService Definition
Access rights
  • What types of patrons should have access?
    Access can be allowed for all users, to only patrons with Active Alma accounts/HK holders, or to specific Alma user groups.
ex: Active Alma accounts/HK holders
  • Should there be limits to the number of concurrent users?
    Access can be allowed for a maximum number of simultaneous users, or have no limit.
Ex: No limit to concurrent user.
  • Should there be a time limit on length of use of object?
    Access can be allowed for a maximum length of time before starting a new virtual session.

ex: 3-hour time limit on length of “loan”

  • Should patrons be allowed to download content?
    Downloads can be explicitly allowed or turned off.

  • Should a use statement be displayed to users?
    A use statement can be provided on screen for the item. 

  • Should use statement be presented as a click-through?
    It is also possible to require this access statement to be a click through (i.e. user must Accept terms before seeing digital item). 

Digital Representation
What type of content will be uploaded?


Who is creating the digital objects?ex: Authors created the content.
Workflow
Do metadata records already exist in Alma for the Digital Representations?
Will digital representations be loaded by staff through the Alma interface, or is a batch load required?