Skip to end of banner
Go to start of banner

2020-05-06 EMWG Meeting

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 3 Next »

Attendees: 

Agenda:

  • Action Items from 4/22 meeting
    • Tiziana will present documentation on the SAHRE-VDE use cases during next meeting
    • Jason: add to outputs: list of detailed reporting functions for future MM-SIG/Reporting SIG engagement
    • For future meeting: what is the approach in FOLIO wrt: data modeling
  • Next step for work areas
    • From Wayne: 

      I think the left-most column should be organized into UXPROD "Epics" (see https://wiki.folio.org/display/COMMUNITY/Getting+Started+for+Product+Owners#GettingStartedforProductOwners-ManagingBackloginJIRA). There are a number of ways to slice this, but broadly I think there are 2 "Epics":

      1. Entity management in FOLIO: Import, creation, maintenance, and publication of entities to be used in resource description. Entities include Works, Agents, and Subjects, the traditional domain of authority control, but the scope could also be broadened to include elements of other vocabularies and ontologies, such as carriers or media types (could use examples from music cataloging or archival management).
      2. Integration of entities into resource description and discovery. This could include the creation of resource descriptions using something like a linked data editor integrated with both the FOLIO entity store and with external data sources, the mapping and linking of resource descriptions into FOLIO inventory records, and the export and publication of resource descriptions as linked data.

      The second column then could break down into UXPROD "Features" under the Epics. There is duplication there, of course, but this feels like a good starting point.I would be interested in Charlotte's perspective as a PO whether these Epic definitions are too broad, and if so, how best to keep track of linked Epics within a related area of work.
    • Charlotte: Epics are huge (e.g: Inventory has one). Should be fine having those two and then we write up those features as he said
      • to cover all, should include UXPROD features for covering authority data in the MARCcat thin-thread features
    • Christie: way that we have reference data set-up is manual in Inventory settings. There is overlap between managing entities locally and what is being called reference data in FOLIO (tables with vocabs, e.g.: RDA content terms)... and the current process for management is not sustainable
  • SHARE-VDE Use Cases


Action Items:

  • No labels