2021-02-11 Resource Access Meeting Notes

Time	Item	Who	Description	Goals/Info
2min	Administrivia	Jana Freytag	Update from the PC-Meeting Acceptance Testing	Notetaker: Martina Tumulla
	presentations by implementing libraries
	documentation		Erin - Continue working on in-app reports document? https://docs.google.com/spreadsheets/d/1Jr1FM9KNVdWZVkx2HcpuDgdBZENsQk5U/edit?usp=drive_web&ouid=101818288105864628077&dls=true
	RA Documentation Review	(OLD ACCOUNT) Erin Nettifee	Set steps for our documentation efforts Documentation group spinning up soon A lot of our basic functionality is already documented: https://drive.google.com/drive/folders/1v2u0rKtYRZxqV5KTssCGDvkgkv11kdzq?usp=sharing What do we think is missing in this architecture? cross-app workflow documentation? more "behind the scenes" docs? e.g., things libraries should know about workarounds, tips for how to do things more efficiently, other? docs for RA features that take place in Users? docs for RA workflows in Inventory?
	the implementation process

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue

Administrivia:

Update from the PC-Meeting: Acceptance Testing
- Testing involvement from SMEs – POs wanted to come to SME with aspects of test involvement?
- SME to work on UAT during development testing
- At RM UAT – there was an environment where data can persists, would be important for RA tests as well
- Bug fest now 2 weeks instead of one week – it is so close to software release to have enough time to fix bugs – goal with testing earlier to catch bugs earlier (Regression testing)
- during bug testing finding spec bugs - catching those earlier would be good too
- Spec Bugs = stories in Jira – built by developer as specified – behaving like it, but not meeting expectations from SMEs
- the Spec is the problem - not the development of the developer
- Developer seem not happy with feedback from SIG (volunteering for tests) – how can we support/help?
- There is a regular PO Meeting and first RA POs will talk this through and will come back to SIG with possible test, if ready
Charlotte will come to the RA SIG with a review of the inventory instances and our preferences

documentation - continue working on in-app reports document

Requests – Export search results
- We also want to include the department in this report – the new users field
Requests - Export shelf clearance report
- Report is greyed out – requires at least one requests in “Closed – Pickup expired” status at the service point where you are in order to be able to run the report.
- How hart is it to change the pickup service point?
- You can change it – it will tell you to put in transit if it was changed afterwards / You can change the pickup service point in the request (status open)
- There were a couple of changes recently and probably more to come.
- Under what scenarios can you change a request pickup point by just editing the service desk pickup point in the request? ...
- Add searchable call number
- Report is based on the service point you are at – service point field is not in the report
- Workaround – to more than one service point is the results list export and filter
- Feature requests for Pick list export for all service point – not developed yet
- If you're trying to do multiple service points at once, you'd use the export search results functionality, which includes the service point of the request.
Inventory – in transit items
- Want machine sortable call number when its available
- Want effective location and permanent location
- Is title check in service point clear enough? Should it be Last check in location?

RA Documentation Review

Erin and Andy (substitute) as representatives for RA and Christine Tobias as representative for UM in the documentation working group
Started the documentation with RA – so there is already documentation which we are reviewing
the working group will talk about screenshots - Concerned about the flux in UI and maintenance
Think about, what to add to documentation
Even if we document certain topics outside of the documentation website
Are there workflow between apps, which we need to document the basics?
Documentations behind the scenes? Workarounds, tips on doing work more efficiently
Website: Step by step for a basic users – nothing on implementation consideration e.g. loan rules
Docs for RA features that take place in users?
Questions: Shouldn’t be the entries for users and Circulation in the left pane closer together?
User is right now in Administration – could be in an own section?
Link from Circulation to User documentation
Users – two aspects as staff administration and for patron management
Circulation log – still missing in the left pane - behind the scene work for documentation – was not included because Circulation log was not in FOLIO by the time Marcia did the left pane in the website
Starting a list for missing topics – so the writers can start with this list/topics