2019-01-25 - System Operations and Management SIG Agenda and Notes

 Integrations which we have not yet discussed:

• Course management integration: Moodle
• IR: TIND, DSpace, BePress, OPUS3, Fedora
• DAM: ContentDM
• Annex/ASRS: Dematic
• Discovery: EDS-API, Beluga, Lukida, Primo, DAIA

Meeting Notes:

SIP2 is needed by many. NCIP is needed by Lehigh. Relais with NCIP.

Course Management Integration:

Moodle is used for ILL. Lehigh has no integration with the ILS right now. For Lehigh, it's a "nice-to-have". Moodle is accessed via Single-Sign-On with the library's ILS. It needs LDAP or Shibboleth integration interfaces, mabye others. Integration of the content (PDFs) is done by a link to the file system, not integration of the file system itself. This is course material, PDFs are provided by university staff like professors. https://www.lambdasolutions.net/services/moodle-integration-custom-development/

IR (Institutional Repositories)

TIND is an evolution of a CERN system. It's Open Source. Old Name of TIND was Invenio. http://info.tind.io/IR

The integration is done by the discovery tool, not directly. In the future, we want to make integration with FOLIO possible.
TIND is a "CRIS" = current search information system. CRIS is established at the university level. One wants to know, for example, how much the university spends on publications.
Need an example of a connection. https://www.exlibrisgroup.com/products/esploro-research-services-platform/ (Marketing Site!)

In FOLIO, after intergrating MARC, integration of also Dublin Core is planned. IRs do something equivalent to cataloguing.

Islandora : The object lives in the Islandora database.

In general, integrating IRs is about discoverability, searchability, visibility. It is not about importing the object to the ILS.

hbz needs link to IR-objects in the bibliographic record (for legal reasons, state archiving obligations for state libraries).

 ArchiveSpace is a frontend.

DSpace is used by many institutions. Bib records have urls linking to IR items. DSpace complies with the standard protocols OAI-PMH / SWORD (v1 and v2) / OpenAIRE and Driver. It provides provides RESTful APIs in accordance with modern web standards. https://duraspace.org/dspace/resources/technical-specifications/ .

BePress is not currently integrated at Lehigh. The future of BePress is open there.

DAM - Digital Asset Management is the same case of appliance as IR . ContentDM is not currently being integrated at Lehigh and is going to be replaced.

At Alabama, the integration to Annex/ASRS is a custom software development. They would like to have the process integrated into FOLIO. Work is in progess. The work is on the end of the customer, not in FOLIO. Alabama uses the Voyager system in their Annex. It's an extension of a request system.

Discovery Integrations

The API for EDS is very similar to something that OCLC makes available. Harry offers a walk-through on FOLIOs EDS integration (likewise applicable for VuFind, Blacklight; others). Will schedule for one of the next SIG sessions. An API was built which will work for EDS, VuFind, BlackLight; all has been done except for "holds". Some performance issues.

Chicago has an automated retrieval system for integration with VuFind.

Patty .... ("good idea")  patty.wanninger, please add this idea here! 

hbz Digibib IntroX  uses a closed interface, possibility to integrate has to be clarified in hbz team.

Beluga used in GBV/VZG is based on VuFind http://beluga-blog.sub.uni-hamburg.de/blog/category/discovery/ ,  https://beluga-blog.sub.uni-hamburg.de/blog/2016/03/18/beluga-core/ (in German). 

Lukida  is an OpenSource development by GBV/VZG. GBV has to expand drivers to include the API. Julian Ladisch volunteerd to do so and will probably do the job within one day. https://www.lukida.org/discovery/ , https://github.com/gbv/Lukida/ .

Real Time Availability APIs

DAIA - https://github.com/gbv/daia; document availability information api . Used by many institutions in Germany for real-time availability .