2021-12-02 Resource Access Meeting Notes

Time	Item	Who	Description	Goals/Info/notes
2min	Administrivia	Jana Freytag		Note taker: Jana Freytag meeting_saved_chat.txt meeting_saved_closed_caption.txt
20 Min	Reporting	Angela Zoss (Old)	Discussion on reporting issues
20Min	Requests	Brooks Travis	request sorting issue: UIREQ-673 - Getting issue details... STATUS

Meeting Notes

Reporting:

Why is LDP transferred to metaDB: metaDB is preferred because it is a more advanced software to LDP
will people have to rewrite their queries after trasition to metaDB - Queries we have might get transferred - but if not it will be happening manually
automatic translation of local queries (LDP → metaDB) would be great
Differences in tables must be taken into account for this transfer
raw data FOLIO → gets unpacked in the metaDB
In first wave of query translation there will be the old json blob still available
Teams for the major SIGs were formed, which are working on building queries
Reporting SIG in the moment is planning to put together trainings for people to ger aquainted with building queries
How does the community deal with changes to the data models (changes to names of data fields, removing data fields, ...)
Reporting SIG does not get the information on changes early enough does the RA SIG get these Info?
- brought up usually on funcional levels by POs
- maybe not often clear to all SMEs but the POs try to point it out whenever it occurs
- Could being part of the AI Group (e.g. being in the loop of changes to the data model) help?
Check Captions for Topic: call number by Joanne
trying to determine which queries are needed:
- two ways:
  - derived table queries (joins data for regular use) (e.g. Item table and locations table)
    - most libraires using these derived table run these queries nightly
  - report queries: run as you need it (result: spread sheet); needed once; general queries (the Reporting SIG needs help to form a standard set)
- The Reporting SIG wants to help people to write their own queries
Future features for LDP: save and share queries
We'll have these valuable Reporting cross meetings monthly from now on

Requests:

"Sort results by barcode" does not sort properly
Problem is the data sync between the business layer module and storage layer module
Situation; sort by item barcode items with empty fields in the searched entities brings up problems
Will be solved by solving the data synchronization issues
Feedback:
- edge case? if the barcode search is still functional then this is ok.
- item and requester barcode
- Could be aproblem for libraries having open hold shelf sorting their books by user barcode situations
- everyone agrees with the priorisation of P4 or P3