2022-01-20 - OA SIG meeting

Meeting time: 8:30 AM (EST) / 1:30 PM (BST) / 2:30 PM (CEST)

Meeting URL: https://openlibraryfoundation.zoom.us/j/82643780981 (Password required)

OA Working Group Wiki: Open Access SIG Home

Google Drive Folder: https://drive.google.com/drive/folders/1HR1JyDkUeRE0kL1eBKcu6uIvcNcnn352?usp=sharing

Slack channel: #open-access-management

Mailing list: folio-rm-oa@ole-lists.openlibraryfoundation.org (Subscribe here selecting 'folio-rm-oa' list)

Housekeeping and major community updates

Agenda items

    • Current development demo (Owen)
    • Sources of people and journals (external sources, on demand creation)

Minutes

    • OS: Demo on request app (incl. outstanding development) and record correspondence functionality
      • correspondence functionality approved by group
      • BM: "last edit date" on correspondence record and list would be helpful in addition to "create date" already existing
      • EDS: no cost information at the moment
        • OS: cost information will be linked to Invoice app; need to figure out whether and how encumbrances could be supported
      • EDS: need to have reporting capabilities
        • OS: some lightweight in-app reports could be possible but for cost reporting and more we need external report facilities like LDP (Library Data Platform) which is still in development
        • BM: depends also on where the system is hosted and which reporting solution/connection will be offered
    • OS: Regarding peole and journals: aim is to add two more tabs at the search pane: people and journals for search and creation functionality
    • OS: Do you rather prefer to upload a list of existing people or created manually on demand? Latter with possible GDPR issue? 
      • EDS: create on demand, no list of people available
      • MB: a list would contain a lot of people that will never publish; GDPR and tech issue
      • CP via chat: same
      • EDS: Is it possible to create the person information within the request app? 
        • OS: discussed this but difficult from tech and workflow perspective because user needs to know that he/she creates an person record
      • OS: workflow could be: search person via tab, create request if person is found or create a new person
    • OS: Same question for journal information
      • EDS: same as for people, prefer on demand manually
      • EDS: information on hybrid/full OA journal needed
        • OS: on the request level because journal level could change over time but we need to know what status on request date
      • PS: What about local KB information?
        • OS: Yes, a way to search and fetch information but difficult to add new journal information
    • OS: on further course of development
      • showing supplementary properties on agreement; similar approach to OA properties planned in agreements
      • list of titles
      • financial aspects
      • task based operations

From the chat


Attendees

Present

Name

Home Organization

x

Owen Stephens

K-Int

xIan IbbotsonK-Int
xGill OsguthorpeK-Int
xBjörn MuschallUL Leipzig
xChristina PrellUL Regensburg

Caroline ZieglerUL LMU Munich

Volker SchallehnUL LMU Munich

Vanessa GabrielUL LMU Munich
xEloisa Deola SchennerleinSLUB Dresden
xLisa SchäferZBW
xMartin BauschmannUL Leipzig
xPeter SbrzesnyVZG Göttingen

Mona OrloffZBW

Astrid OrthSUB Göttingen

Cornelia Lang

UL Regensburg

(proxy Christina Prell)

xPeter McCrackenCornell University

EthanK-Int Dev

Sam HepburnK-Int Dev

Frank Manista

JISC UK


Simone GrunerSLUB Dresden

Michael WolgemuthSLUB Dresden
xMichael KozybaUL Braunschweig
xDavide Del DucaUL Chemnitz

Jack Golding