Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Date
Attendees
Goals
Discussion items
| Item | Who | Notes |
|---|
| Minute taker? | Kirstin Kemner-Heek |
|
PC Updates - Minutes
- Implementation timelines
- Interest in ERM
Discuss posts of Interest:
| | - FOLIO release "aster" is coming out in 01/2019. PC discusses implementation plans for FOLIO.
- Go live is pushed from 2019 to summer 2020 by Chicago, Cornell, Texas, ... but ERM could work as partial implementation.
- German libraries: Leipzig, Dresden, Freiberg, Bremen, ZBW, Lüneburg do plan to go llive with ERM as soon as possible
- Stakeholders meeting on Tuesday next week for more information
- ERM: clarification about requirements - work by Ian and Khalilah to be put in Jira
- How to push development forward in the working groups? Martina, Martina, Kristin will work on that
- ERM: new development: outcome of the Sheffield meeting are planned to be shared
- Ian: more work and detailed requirements will be put into JIRA to have a better overview and full understanding
- Ann-Marie: will give us an overview about the ISBN discussion next week - please view and participate in the discuss post in the left column
|
| Acquisitions Progress report | | - http://folio-snapshot.aws.indexdata.com/
- Vendor app:
- contact information with multiple contact people
- manage contact information in the vendor record
- Do we need a contact module?
- Bug fixes are in focus of developement recently but analysis looks at the enhancement regarding "contact app"
- wiki: "vendor module entities"
- enhance managment of contact details, like emails, phone numbers
- Vendors = organizations (content provider, platform or access provider): can we match the entries from ERM orgs and vendors?
- Vendors will have this requirement regarding organizations to be used in other apps like ERM / eHoldings - shift for the module
- Vendor organizations with different roles
- Option: a vendor is not necessarily an institution sending invoices (paying / non-paying vendors) - needs to be indentified by a key (checkbox)
- Validation check of vendor names before loading data
- Reporting needs: show me open orders of exactly THIS vendor
- Authority control for vendors?
- But: vendor file shouldn't be the area for contact management
|
Action items