2020-09-03 Metadata Management Meeting notes

Former user (Deleted)

• Bound-with conversations with developers continue. There will be questions for this group in the next few weeks.

Jason Kovari

https://docs.google.com/document/d/1FaFYCXZIY-dN3QnifITi233q0GmVQqUJcUUSJlv-56s/edit?usp=sharing

• Group is comprised of MM SIG and non MM SIG members.
• Charge:
  • How do we do activities traditionally considered to be authority control in FOLIO, beyond MARC?
  • How do we engage with entity based data models like BIBFRAME?
  • Note: This is not a linked data group.
• Entities
  • All entities considered: Agents, Genres, Subjects, MARC Relators, Work Enttities, etc... Broad definition
  • There is no singular source of entities for each type. Brings up crosswalk issues
• Vision statement defined a separate application within FOLIO for this app.
• Interaction app group was attended, and some interest from that group 
• Conceptual diagram, architectural considerations given in document
• Rational for separate app, along with recognition of work being done for traditional authority work by former MARCCat group.
• Codex section and considerations will be added.
• With feedback from MM SIG, this document will be shared with community and presented to Product Council
• Wayne commented that Jason gave a good summary, and thanked Jason for leading the working groups.

Questions:

Ann-Marie - How will this relate to authorities and source record storage? Will this end up in pool of general resources or are resources identified. Jason answered that he would look to Laura and Dracine for guidance. No effort has been made. Resources out of purview for this group. 

Dracine added that this could be part of the discussion of the new Vision and Strategy Group.

Jesse: Can you imagine any specific hurdles in development for this across apps? Or is that challenge just assumed? Answer: Assumption is that this will be difficult. 

Ann-Marie - For development, the various development teams will be affected. Product owner would need to lay out sequencing. Jason - Not just editing, but "additive". One point is that reference data would move into Entities Management space. 

f-piscitelli - (question via app) - Would this app incorporate info. from Wikidata? Answer from Jason: "Could be 'yes" " ) This is beyond the vision of the app itself. 

Wayne - Cross boundary interactions is a challenge in the FOLIO environment in general. Suggested that that challenge may need to be addressed on a higher level before sequencing happens. 

Jason - Wayne and Charlotte brought perspective on the difficulties on cross-app. Should outline

Theodor - "The importance of exposing local entities to the outer world is key I believe. I saw it is mentioned in the doc, but kind of briefly."

Laura - Pointed out the scope includes, importantly, having a separate app. If someone thinks a separate app is not a good idea, please give feedback/argue

Ann-Marie - Envisioning triple stores? Answer - Jason - did not get into that level in planning. Does not need to be a triple store, but could be. Technical council will be engaged in that discussion, hopefully. Group was more concerned about how do entities engage with other aspects of FOLIO.

Patty - Why not allow for linked data, triple-store? Answer: Group was not prescriptive with underlying technology. Patty - This is an important piece for going forward... Answer: Not ready to make that statement about the necessity of having an underlying triple-store. That may not be the case. Internal data may not have to be in triple-store. 

Question: Is this supposed to be a "helper app" or an app on its own. Answer: It is intended to be its own full app. It will need its own sets of records, defined by a user via settings. There is data stored in that app that can be stored in that app. Needs to import data, push data out. 

Patty - Sounds expensive. Answer: Not yet considered/addressed. Prioritizing and addressing will contribute to what resources will be dedicated. Laura - Community priority will be a factor. Jason - Priorities now are "go-live" what do we absolutely need. This gets into the point of long-term priorities - addressing development in terms of long-term needs. 

Ann-Marie - This could be the type of work a group of developers that find the work interesting may want to take on. Developers not involved currently in project may join to try this ...

Wayne - It would be difficult for this to be an independent project because of the cross app integration that will be needed. Not impossible, but difficult.

Jason - This is more of a strategic direction than a "go-live"

Christie - If we want FOLIO to be well positioned for the future, the project will include this. If it is not, institutions will find ways to do this on their own. This will be problematic for the project.  

Entity Management Epic:  UXPROD-787 - Getting issue details... STATUS

Laura - timeframe? - Jason - up to MM SIG. Laura will propose that feedback time for this given will be two weeks time.  Questions? - Reach out to Jason. 

Felix Hemme

Theodor Tolstoy