Skip to end of banner
Go to start of banner

2023-05-04 Metadata Management Meeting notes

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 5 Current »

Date

~ 

Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/

Discussion items

Notetaker


Announcements



PC update

Sharon Wiles-Young


  • Technical Council is discussing a draft on browser support and would welcome questions or comments
  • Changes to hot fix release process from Oleksii in Slack: 

    I want to inform you, that started from Orchid release (R1 2023) we are replacing Hot Fix process with Critical Service Patch (CSP) process.
    You can find detailed presentation about it by link - https://wiki.folio.org/display/REL/Critical+Service+Patch+Process.
    Benefits

      1. Provide a clear and documented process for requesting a service patch
      2. Reduce number of changes for post GA releases
      3. Reduce time to market for post GA changes (will be released and announced once ready)
      4. Helps to reduce context switching for development teams
      5. Formal process helps to ensure the reliability and stability and minimize the risk of service disruptions
    • Product council and other hosting service providers should gage and report on the impact of this change as releases are deployed.
  • PC returned to the discussion of Role and discussed the reality of PC role in the FOLIO project: Action items are: 
    • Clarification of PO to development team- some POs do not have a development team to report to
    • Think about a coordination role of PO or some other role to bring in PO resources/development resources
    • Figure out a process to onboard and have development resources in the community pick up some of the development work-blocked JIRAs, bug work, sprint development needs?
    • More closely align FOLIO roadmap priorities with development teams and PO work
    • PO have lots of responsibilities realign some work and have SIG do more initial testing before bugfest testing?
  • Workflow SIG: Martina S. will be writing a draft proposal for this SIG-last week Jeremy Huff from Texas A&M talked about development of workflows in FOLIO using Camunda as the workflow engine

Jennifer Eustis 


MM SIG Release Note & Other Highlights



Proposal to make the call number a repeatable element

André Hohmann 

Felix Hemme 

https://wiki.folio.org/x/ZUu-BQ









Chat:


  • No labels