2018-05-31 Metadata Management Meeting Notes

Date

Attendees

Goals

  • Finish review of Holdings UX

Discussion items


Product Council update

QA consultant hired: Anton Emilianov[sp?] on temporary basis, will report to Cate Boerema, starts June 11

University of Leipzig has joined OLE will be contributing 2 developers (ERM) and 1/2 FTE Product Owner

Proposal for new Technology Council. Technical Council will help Product Council prioritize developer time, help address technical issues, long term vision, continuity of platform. Once this is solidified, Dracine will pass along the charter for the Technical Council.

The Community Engagement Group will be addressing issues concerning effective communication.

How will the Technical Council members be decided? The membership will be decided by the stakeholders group: OLE, EBSCO, Index Data.

Subgroup updates


  • MARC Batch Loader - The group has finished going through use cases. The group is limiting the scope to bibliographic and acquisitions data. A list of requirements is being made, and prioritizations are being assigned. The requirements will lead to features that will be reported in Jira. A list of sources of vendors that provide bibliographic/order data is being established. Anne-Marie will be out for a few weeks. In her absence members will be demoing their import processes and tools.
  • MARCcat - Charlotte has had several meetings this week with Tiziana, the PO for the MARCCat App. There will be a small group with participants from the early implementers group is being formed. There may be two meetings per week. This group will work as a support group to Tiziana and her work. Hoping for its first meeting next week. Charlotte will be helping as well.
  • Local Package Record - Laura reported that they have volunteers and will be convening next week.

FOLIO Inventory definition

FOLIO Codex Search definitionLaura E DanielsThe same process will happen for the Codex. Charlotte and Laura have begun this process. Charlotte wondered if this will be done for all apps. Dracine thinks this could become a regular exercise for the community. The eholdings app may be next. Peter Murray suggested using the wiki to list these definitions. Dracine suggested linking to these pages from the glossary that is being created.
HRID

Human Readable IDs:

The UUID is a system generated global unique identifiers. These will be "behind the scenes" ids. The human readable IDs will be alias for the UUID. Niels - How do we want these to look?

  • Laura - shortest possible. Numbers to be communicated most clearly to each other.
  • Anne-Marie - Is this a decision to be made at the system level or app level? Acquisitions has codes that represent the vendor. The instance record has multiple identifiers. This is a record number, a record identifier. A short, sequential number to uniquely identify this record.
  • Laura - Current system numbers begins with an alpha number. Bibliographic record IDs begin with "b", item ids begin with "i". This helps with immediate identification of what type of unique identifier is being stated.
  • Anne-Marie asked that if we do use letters, they should not be case sensitive.
  • Felix (via chat) - "

    As we decided in the Holdings/items UX meeting to exclude the UUID from the detailed display, I just wanted to make sure that it's still included in the URL, so that everyone can see it. I assume the answer is 'yes'." Charlotte assured it would be.

  • Natascha (via chat) - "Is there any chance we would be able to migrate the bib number identifiers we use in our current systems into FOLIO?" - Yes - these numbers would be kept (Charlotte).

  • Anne-Marie - Storage of these UIDs should be same on export and import

Laura asked that further comments be put on the discuss post. Examples will be posted.

Inventory UX

Reminder to view the Discuss post and comment if you have comments, questions, or concerns (or to tell Kimie how much you like something!):
https://discuss.folio.org/t/ux-redesign-of-the-inventory-review-of-the-instance-record/1837

Instance record:
1.Real data
https://drive.google.com/open?id=1Oq-RfAYB0Mv3arHXvPRKqqxvcnVtO7kl
2.Real data expand
https://drive.google.com/open?id=1QmgO0mKRQGRgiZMstm_jLfxSbbYGxf-m
3.Edit instance
https://drive.google.com/open?id=1-FIO06RTYSB6FGT7rFPnitAxs7AIbjgz


Holdings UX/UI

Latest update from the working group and Kimie:

Holding record:
1.Holding data
https://drive.google.com/open?id=1KeHWC2ffzN42DVWlM644_aHRpd-VQVWS
2.Edit holding
https://drive.google.com/open?id=1JaFwL2BBHgpW8Q-cjZNn5FqgUuBoAWCc

  • Should make more sense with "real data"
  • Anne-Marie asked if there is a MARC record with 856 field with a URL - will that go into the Instance record, Holdings record? It will go into the Instance Record right now. They have not talked about if it should be in the holdings. Optimal would be if a user could choose. Right now there is not a place in the holdings for a URL. Charlotte said she would add a new element called holdings ui. She will talk with Kimie about this.
  • Batch Import group asked if the URL placement could
  • Felix - See Line 5 of the composite_to_folio_inventory.xlsx doc.

Action items