2018-07-06 Joint RM/Inventory/ERM Meeting

Goal of this meeting is to better understand the relationship between Inventory/RM/ERM/EHoldings

Major questions to be explored included:

• Relationship between Local packages in Inventory and Packages within ERM
  • Are definitions harmonized?
• Relationship of e-holdings and inventory holdings
  
  • Placing fields within In
• Relationship of licensing for non-ERM items  (e.g., archival collections, others?)
• Understanding cross-app needs in general

Background documents and reading

• Draft Terminology Document: https://docs.google.com/spreadsheets/d/1jRn-_ayyoBdNJ2hr5Rf_QtUjjczT-r10hQ0q_PGG77k/edit#gid=0
• Cross RM Apps Capabilities and Dependencies: https://docs.google.com/spreadsheets/d/1zyMQZlN-00GJJ-VzZNuBUGfGA0dwCrRY6_b_haDGGhI/edit#gid=0
• Local packages in Inventory: https://docs.google.com/document/d/1DakHW6D5_09uKJPQzCSTwycP0gqkPs6E7k35_KpfCxg/edit

• JIRA Features with the label crossrmapps to represent a dependency on another RM app(s): https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=32&quickFilter=222

• eholdings integration workflow: https://docs.google.com/presentation/d/1MbcUHphAdV30WQg5ZLZK1Ohmu7cIkr8p_E74QmejJEw/edit?usp=sharing

Cross RM Apps document - Outlines features that in the various apps, outlines who owns them (kicking off workflow, owns data), what is the role of each app in the features along with development status in that app. These are listed as "dev" and dependency (requires coordination between 1 or more apps, POs will need to discuss).  Once an agreement has been made on the dependency features, they move to Dependency - Analysis Complete, and so on. Hopefully, can identify all dependencies and then prioritize the functionality for development. Comments and relevant JIRA links are listed.

Ex. "Search KB" - search a kb, currently EBSCO's kb. Eholdings development is done. ERM is currently set as N/A - would ERM need to search the knowledgebase? It's been marked as N/A because the intention is that the data would be brought from the KB into ERM (it would be harvested) through KB integration and then you would search the ERM, search the process the ERM knows about (normalization done during the process). ERM would have a copy of the KB. There is overlap between ERM and eholdings. If two KBs communicating with Eholdings, how would this work? There hasn't been a use case for this yet, there would probably be two back-ends tied to the same front-end. Still discussions regarding the role of search KB with Acquisitions. Is this a job for the Codex?

Relationship between eholdings and inventory?  If you have a journal in eholdings, is there a local instance in inventory and/or ERM? You will have a record in Acquisitions, should automatically be in ERM? Where else will it be? Comment: Folio should be able to support libraries that want to create a local record and those that do not. Charlotte and others are trying to gather cases where data needs to flow seamlessly between the apps - FOLIO-1273.

Comment: not convinced that Holdings Management CRUD local/custom packages are relevant to ERM so no dependency listed. Could lead to duplicate work.

Overlap vs. dependencies. By focusing on overlaps, are we limiting what work can be done? More than dependencies, the documents lists the features that need to be supported and where that support should/may come from.

Discussion on packages (local packages in Inventory document)

If you create a package (or virtual container) can this type of record be used across apps? Can an ebook be in multiple packages? Yes. Does inventory need to know about packages? If purchasing a package, we would want this in ERM.  Eholdings provides a way to create the container, would it be possible to use it for these cases? In the list of use cases, can some of these be addressed by tags? There are institutions who would want to group things within inventory.

Will aim to meet again in 2 weeks.