Development progress - ERM sprint 173

ERM-3010 Add has/has not filter in Agreements

• New filter for agreements to search for agreements that have or have not special aspects of their metadata sets – new set of filters that can find all agreements which don’t have an organization yet – helpful for workflow – work in progress 

• Gill has done some designs – ability to add to filter 

• Right now has or has not as filter functionality 

ERM-3018 Implement GOKb Title UUID as primary match ID where available

• Reliability of synchronization process

• Data from external source – representation as accurate as possible in FOLIO 

• Working on using the GOKb Title Identifiers to make sure we have a work in FOLIO

• Aiming for poppy release

• Much more reliable one to one correspondence between a title in GOKb and the data in FOLIO

ERM-1795 Dashboard: apply a common set of drag and drop styles and behaviours

ERM-2979 Add agreement line summary information and navigation link to Agreement edit view

• Removed the Agreement lines from the agreement edit page, but now there is a link to the Agreement lines from the Agreement edit page – display the count as well and you can open it in a new page without performance issues 

ERM-2993 Add amendments search in licenses app

• Additional Amendments’ tab to search and filter by status, start date, end date and terms 

One piece of work I am hoping to start next sprint – search for Agreements based on documents attached – will start development

WOLFcon update

1. Knowledge base session: Update on work related to GOKb sync

   1. ERM - connecting KBs as metadata sources

      • Joined session: Martina S.: Using GOKb integrated with Agreements at GBV / Owen: description of the current options for integrating knowledgebases with FOLIO Agreements

2. Dashboard sessions: Update on dashboard use and extending dashboard session

   1. Expanding dashboard:

      • expanding the dashboard – technical aspects 

      • Use cases for Dashboard development for ACQ

   2. Dashboard app and its benefits in daily life: library demos
      
      

      • Presentation from Daniel Kirst and Felix on their dashboard use

      • Daniel’s presentation included organizing information on dashboard – multiple dashboards, they tagged agreement by content type and one dashboard screen per content type

      • At the moment not yet the option to filter by the new agreement content type field - will be worked on

      • Felix mentioned some improvements for the dashboard maybe for additional development

3. License session: feedback from real world use of licenses

   1. Managing Licenses using FOLIO Licenses App: library demos
      
      

      • Julie (Duke) great to capture their workflow- raised some issues and requests for minor improvements

      • Better connecting organization and contact people

      • New Functionality in orders: edit history

4. From Kbs to KBARTs: ERM data migration into FOLIO

   • • Methods of loading bulk loading agreements and organization into FOLIO and maybe the need for more UI based methods in the future

Preliminary: discuss what other knowledge bases could or should be integrated with Agreements local knowledge base

• It would be good to watch the recording "ERM - connecting KBs as metadata sources" before discussing it

• Mechanic of how to get data from one to another

• Thinking about structuring your KB and how does this relate to the agreements you are creating?

• Titles and packages and packages contain titles

• Set up an agreement: could be a package (e.g. Jstor package) or individual subscriptions

• Zorian: Jstor agreement – each agreement line would represent a package assuming they have the same start date and license terms

• Explaining an Agreement: Set of content covered by the set of same license terms for a defined period of time

• Agreement line per package, per title or a mixture

• How does my external KB represent package - how do I link it to an agreement?

• If you are not using GOKb or EBSCO solutions: Are there other KB/metadata source where you wished to be integrated?

• Sara: You cannot have multiple resources – had previously SFX - integrating feeds automated KBART – found this valuable

• Vendor supplied data (KBART Automation → Springer, Wiley, Elsevier, T&F, Ovid, IEEE?)

• KBART Automation: Automated Retrieval of Customer Electronic Holdings

• Jessica (chat): Chicago's currently using SFX and would love for that to be integrated. That being said, we are conducting a review of KBs now that includes 360, OCLC's Worldshare, and EBSCO.

• Sources outside of traditional KB scopes auch as Kanopy streaming video ...

• Zorian: KB are tied to discovery tools - goals to decouple those 

• Phil (chat): DMU are asking EBSCO about regular MARC imports for Kanopy data

• internally Inventory

• detailed discussion in one of the next meeting: include people who know about data, know about moving data around (export), technical knowledge, tech support, system librarians, metadata librarians