Prioritized In Process Projects
|Requestor||Request Date||Target Completion Date||Size||Priority||Title/Scope||LTS Lead||Library Owner||Impact|
|Alma Tech Team||1/1/2017||See individual items||Medium||High||Data updates that adversely affect workflows||Laura Morse||TSWG|
Workflows will not be possible without key updates to data in Alma
|Alma Tech Team||1/1/2017||See milestone timeline at OCLC Data Sync (Maintaining Holdings in WorldCat)||Large||High||OCLC Export - Creation of Alma to OCLC scripts for maintaining holdings||Allison Powers||Alma created holdings will not be in sync with WorldCat. Requires full synchronization of database prior to ongoing maintenance processes. There are several Harvard prerequisites prior to starting the synchronization for each symbol.|
|Alma Tech Team||1/1/2017||3/30/2019||Small||Medium||ETD loads||Corinna Baksik|
New DASH / print dissertation records not represented in catalog
|Alma Tech Team||1/1/2017||4/30/2019||Small||High||IRIS exports||Corinna Baksik||Lack of new/updated BER data in Italian research consortium|
|Alma Tech Team||1/1/2017||1/30/2019||Medium||Low||Alma Item file export for GFA||Laura Morse|
HD GFA accession checks relies on copy of full file of item records. Need to work with GFA to both ingest Alma item xml as well as revise checks for Alma coding.
Analysis underway with GFA to determine if this check is still needed.
|Alma Tech Team||6/30/2018||12/24/2018||Small||Low||Items to be withdrawn that are on loan or have open POL||Kara Young||Unavailable items remain in Alma|
|Leila Smith||7/3/2018||2/28/2019||Medium||High||RAPID ILL Implementation||Michael Edwards||Develop and implement the publishing profiles for sending Harvard Library holdings to RAPID. LTS work complete, test file sent to RAPID. Waiting for confirmation from RAPID before marking as complete.|
|Marty Schreiner||9/4/2018||11/30/2018||Medium||Medium||Updated POE, DOC, and MIC to be LAM locations||Kara Young||Lamont would like to incorporate these libraries as Lamont locations.|
|Sharon Bayer||11/2017||12/31/2018||Medium||High||Webhooks||Tim||Preliminary use of Alma webhooks to monitor success of Alma jobs complete. Enhancement needed to add in database, etc.|
|Alma Tech Team||10/2018||Q3 2019 (Pending ExL development; see SF case no. 673074)||Medium||Medium||Create invoices via API||Bill Walsh / Tim Elliott||Use invoice APIs to create invoices for vendors unable to supply EDI invoicing.|
Karen Carlson Young/Rebecca Martin
|February 2019||Small||Low||Create items||Kara|
|HUA/Kate Bowers/Marilyn Rackley||March 2019||Medium||Low|
Clean up items
|Kara/Corinna||Create 200K+ item records for HUA Aeon implementation.|
|Alma Tech Team||1/1/2017||Medium||Medium||Ebookplates||Corinna Baksik||Lack of digital bookplates in HOLLIS for new receipts|
Requests To Be Prioritized by the Alma Executive Committee
|Requestor||Request Date||Requested Completion Date||Size||Priority||Title/Scope||LTS Lead||Impact|
|Alma Tech Team||1/1/2017||Medium||Medium||Aleph Library Reporting Warehouse Data Updates - Updates Cognos System to include Aleph Archived Data||Allison Powers||Data like the full order log, item history, request history and z00r did not migrate to Aleph. This project will provide access to this this data via Cognos. Tables to be added to Cognos: HVD01.Z00R, HVD60.Z00R, HVD10.Z00R, HVD12.Z00R, Order, subscription and invoice log (Z71), Hold Requests History (Z37H), Item history (Z30H).|
|Alma Tech Team||1/1/2017||Large||Medium||Ingest of Alma Bibs/holdings/items into Library Reporting Warehouse/Cognos Data Model||Allison Powers||Allow for crossing data sets with HD data and other reporting needs.|
|Alma Tech Team||1/1/2017||Small||Low||Generic Alma Export||Corinna Baksik||No one has requested a specific ongoing export.|
|Alma Tech Team||1/1/2017||Medium||Medium||OCLC BNS for Books and Serials (but needs Datasync first)||Corinna Baksik||Lack of valuable updates to bib records with new data from OCLC|
|Alma Tech Team||1/1/2017||Medium||Medium||HFA loads||Corinna Baksik||Lack of new/updated HFA data in HOLLIS|
|Alma Tech Team||7/1/2017||Small||Medium|
Mispaired non-Latin fields flipped to vernacular
|Corinna Baksik||Loss of non-Latin data in local records. (More detail on Known Issues page)|
|Anne Adams||9/27/2017||Small||Medium||OCLC sync for p level records (RECCO/MUS)||TBD||In an effort to provide better access for recordings that have H08$ap level cataloging, a batch overlay of these records with updated OCLC records (I and blank encoding levels) could provide better access points for older records, allowing us to possible change them to H08$ac. |
More information in ALEPH SUPPORT: ISSUE=21777 PROJ=14
|Rachel Lewellen||5/1/2018||Large||Low||Ingest of Alma Local Backup Service data in Library Reporting Warehouse||Laura Morse||Certain Data Elements may not be available in Alma Analytics for reporting. In addition, some data points may be needed in LRW to cross with other data sources, like HD data. This project would evaluate whether a subscription to this service and ingest of data into LRW would meet assessment and reporting needs not met by Alma analytics directly.|
|Andrea Schulman||5/31/2018||Small||High||Capital IQ||Kara Young|
From Andrea: Like the wsj.com, it will require individual logins. They are implementing SAML for single sign-on. We have also proxied a page where new users can register for an account with a Harvard email.
|ADSC?||1/1/2017||Small||High||OCLC Holdings Symbol Consolidation||TBD|
|Baker||5/1/2018||Medium||Medium||Baker 3.0 API Project||Laura Morse|
|Laura Wood and Anu Vedantham||6/4/2018||Medium||Medium||FP Data Harvest for planning||Lindsay Whitacre|
|Rachel Lewellen||5/25/2018||Medium||Medium||Updates to HD data model in LRW|
Update LKUP_HD_OWNER table by adding a column for "Customer Group" and populating with the entries provided in an Excel spreadsheet.
|Wendy Gogel||6/15/2018||Medium||Medium||Adding VC subject data to Alma records||TBD||VC included a local database that stored additional subject data not present in underlying database of records. With migration of VC to Spotlight, this data needs to migrate to a new home. This project is includes investigation of possible fields in Alma MARC records to store these subjects (they are not a controlled vocabulary), as well as planning for load of data into Alma.|
|Suzanne Wones/Franziska Frey||6/30/2019||Medium||Medium||Hathi Annual Print Holdings Disclosure|
|Redesign process for the HathiTrust “print holdings” report.|
|Permanent Retention notes||6/19||Large||Medium||Adding retention notes to records||TBD||Adding retention notes to support collaborative partnerships (Hathi, ReCAP, LoR, JSTOR Retention)|
|Google Scanning||5/1||Medium||High||Alma export and tracking processes||TBD|
|Hathi Disability Disclosure||6/15||Small||Medium||Update holdings in Hathi||TBD|
|Publishing Strategy||6/19||Medium||Medium||Support various full file publishing||TBD|
|Library Kiosk Machines (increased HOLLIS logout time)||5/20||Medium||High|
Ensure that all library public terminals have kiosk accounts
Issues with HK logins on shared public library terminals
This project would allow all HOLLIS users to have an increased logout time so they are not logged out after 45 min, a significant complaint from patrons and staff.
|Berenson||7/3||Small||Medium||Potential patron loader changes||Kara Young||Berenson visiting scholars currently come through patron loader as staff members. This results in longer loan periods than Berenson would like for these short-term visitors. Analysis is required to determine whether such a change is possible.|
|Shalimar White||7/2017||Medium||Medium||Consolidate Rubel collections in Fine Arts||TBD||Circulation and management of Rubel collections separate from Fine Arts present issues with patron interfaces (Rubel appears as a pick-up location) and with staff workflows (staff have to flip "currently at" location to discharge Rubel items to put "in place"). Consolidation would simplify patron request options and provide more efficiency in circulation workflows.|
|Alma Tech Team||1/1/2017||Small||Low||Longterm HD loans||TBD|
Determine if issues still exist with items in transit to HD/ReCAP not appearing in end of day files and requiring periodic reconciliation
|Alma Tech Team||1/1/2017||Medium||Low||Hey Carrel||TBD|
Local development of a web app.
|Alma Tech Team||1/1/2017||Medium||Low||Inscriptio enhancement||TBD|
|Alma Tech Team||1/1/2017||Medium||Low||Library Services Dispatcher - Phase 2||TBD|
|Alma Tech Team||1/1/2017||Medium||Low||Open Metadata||TBD|
|Alma Tech Team||1/1/2017||Medium||High||Library Cloud||TBD|
|Alma Tech Team||1/1/2017||Medium||Low||GLIB (FIG Updates)||TBD|
|ITS||7/31/2018||Medium||Low||RequestsTracker||TBD||System is used to triage requests largely from selectors and route internally to ITS departments. Project would analyze ways to utilize Alma or other systems to replace this system.|
|LTS||8/9/2018||Medium||High||EzProxy to CAS||Kara Young, Lindsay Whitacre|
It is proving problematic implementing changes to AMS while it still has to support the EZProxy gateway. I know that it was planned to move EZProxy off AMS and on to Shib/CAS. It would be very helpful it that could be done as soon as possible.
|HLS||8/17/2018||Medium||Medium||SHARIAsource project (http://ilsp.law.harvard.edu/shariasource/||Robin Wendler (analysis)||Replacement for metadata for lilCloud.|
|Laura Morse||9/5/2018||Medium||Medium||Alma Widget - Receive Item||TBD|
Create an app that will accept a file of barcodes and receive the item to remove acq status
*Request for prioritization 4/18/2019
|Small||Low||Safari/O'Reilly SSO authentication||Kara Young||Authenticate SSO users with Shib (or other options)- analysis required.|
|LeWG||5/17/2018||Medium||Medium||Create a view of reserves lists in HOLLIS||TBD||Allow users to access lists/find materials in HOLLIS directly. Useful at circulation desk when trying to find the item needed.|
|Lidia Uziel||Small||?||Document process for allocated fund batch updates||TBD||Create workflow to allow libraries to generate sets of order records and submit requests to update of allocated funds.|
|10/19/2018||06/30/2019||Large||Medium||Phase 3/Long-Term Alma Training||Jennifer Koerber||Develop and launch a sustainable training platform for staff to work through under manager supervision. Will be developed in the first 6 months of 2019.|
|Lauren Syer||10/25/18||Small||Medium||Fully automate update of Harvard holdings in BrowZine||TBD||Improved user experience with BrowZine with up-to-date holdings; non-automated process subject to human error.|
|Cynthia Churchwell||10/15/18||Small||High||Onboard HBS for Leganto||Kara Young|
Allow HBS faculty to add Course Reserves in Canvas Course Sites.
Project includes: Integrate HBS Canvas Course feed to Alma, training of staff on workflows, Alma configuration
|Suzanne Wones||10/24/18||Small||High||Export Google Scanning Metadata to Hathi||Benson Smith / Allison Powers||Hathi will download GBS scans and provide access to Harvard Researchers.|
Create process to export google scanning metadata to Hathi.
|Elizabeth Vernon||11/15/2018||?||Medium||Conversion of Harvard Alma 966 fields to 853/863 Pairs||TBD|
An important feature of Alma Analytics reporting is that Analytics contains a summary holding field, making it possible to easily include holdings -- including serial holdings -- in a tabular report. This data is critical for the purposes for collaborative collection development with our ReCAP and Ivy Plus partners -- to identify strengths of and holes in holdings. This summary holdings information also serves to support several other key areas of library operations, including periodical deduplication and weeding, digitization projects, remote storage transfer projects, and more. However, any holdings data stored in a 966 field is invisible to Analytics.
The Analytics summary holding field is populated with the aggregate contents of the 866 fields in the holding record. The 866 fields in Alma are generated as display versions of the 863/863 fields.
The data that was previously stored in an 866 field in Aleph was converted as a 966 field in Alma. The old 866 (now 966) holdings data includes both serial holdings that were done in summary form (particuarly from retrospective conversion projects of periodical holdings recorded on cards, but also certain categories of more recent titles), as well as holdings for monographs and collections.
The problem is that the data in the 966 field does not populate the Analytics holdings summary field -- it only recognizes the 866 field. This means that the holdings for approximately 783K records -- of which 173K are serials -- display as blank fields in Analytics. Without this holdings information being reportable through the holdings field, compiling this data will be complex and time-consuming.
The remedy to this problem is to convert the data in 966 fields 853 / 863 pairs via batch job, according to the following pattern:
853 02 $$8 1 $$a (*)
|RMWG||11/25/2018||Small||Low||Correct 2nd indicator and $2 for 655 coded as LCSH and flipped by Alma to LCGFT term||Corinna Baksik||When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft). This does not have an effect on patrons using HOLLIS, but the incorrect coding may cause problems in future linked data projects or migrations. Alma will continue to flip these headings so on-going clean-up may be required until after/if the Ideas Exchange is implemented:https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/36105922-preferred-term-correction-correct-coding-when-fl|
|Leila Smith||12/6/18||?||High||HD Accession Checks||TBD||With accession checks currently off in LAS, we are anticipating a fair amount of errors that will impact patron requests. For example, an item that should be refiled at ReCAP, that was never on file at HD, might be accessioned into HD instead of being returned to ReCAP. The longer these checks aren't done the way they used to be, the more cleanup there will be down the road, which could leave a number of partial trays. Cleanup work is also contingent upon ALMA data in Cognos.|
Vitaly Zakuta for:
|3/6/19||?||Medium||Bulk-create holdings with URNs to DRS items||TBD||Multiple repositories previously used Aleph functionality to bulk-add new suppressed (or unsuppressed) holdings to existing Bibs with URNs to DRS items. The old process took a CSV of HOLLIS numbers and URNs and then created new digital holdings with URNs. These repositories would like Alma to offer similar functionality. This is especially critical for large scale projects when thousands of records in Alma need to be updated with new digital holdings with DRS URNs.|
|Alma Tech Team||3/7/19||Low||Items with Item Policy 88 (Suppressed) (These display to the public)||Corinna Baksik||These items were suppressed from display in Aleph, but are displayed to the public in Alma. In Alma you can suppress entire holdings, but not individual items attached to holdings. Sometimes units have these items and just didn't want them to display to the public for misc. reasons; in other cases the libraries no longer have the item. Items with this policy are not requestable by patrons.|
|D2D||3/27/19||Medium||Outstanding data clean-up for closed libraries||Corinna Baksik||Numerous reports were distributed prior to migration for data from closed libraries that needed clean up. Staff are reporting seeing holdings for serials but the item records are not available. Example: 32044072903669 is attached to a Littauer holding which is suppressed from display, but this volume in listed on a WID HD holding indicating that we should have it, but because the item is attached to the suppressed holding there is no way for a patron to request it|
|Kara||5/17/19||Small||Medium||Batch process to close work orders||Kara Young||There is currently a way to batch create work orders in Alma, but not a way to batch close them. We have several high volume departments (Resource Sharing, Imaging Services) which have hundreds or thousands of items waiting in work order requests that need to be processed through the work order process. There is an Alma API that we could use which would allow them to batch change status and close work orders. I think parts of Sharon's original scan-in items script (for Remote Storage) could be possibly be reused for this purpose. Boston College also has successfully coded something that we could possibly re-use.|