30 min | Demo of new prototypes for workflows and to-dos | | See http://ux.folio.org/prototype/en/workflows. Filip will record a video later today and post on Discuss. Even before the video is out, you can click the “Comment” button on the link above to add comments / ideas / advice on the concept - Workflow steps could be things like
- Fill out forms
- Rudimentary programming/querying
- Keyboard shortcuts
- Alert a person to do something
- The workflows app may start fairly simple (moving some task along a workflow, and telling people about work they need to do) and then become more automated and more complex as time goes on.
- A lot of workflows that are a culmination of automated steps and then stops for a person to have to do something. There’s value in starting to codify those steps, with an eye toward more automation down the line.
- Workflow app will have lots of uses in acquisitions. Maybe start with some of the easy parts of acq workflow, e.g. statuses
- Other Acq-related workflow ideas
- FTP invoice file and park it in a holding area, then alert someone in the library that it’s ready for action
- Keep track of the licensing steps and be able to push a license along a flow of people/departments, but not until certain steps/criteria have been fulfilled
|
| 60 min | Order Physical Monographs - Happy Path Work Package Review Work package here. Comments close at the end of day (Mountain Time) July 19, 2017All work packages and slides are here: https://drive.google.com/drive/folders/0ByKXfvKzMDq-SldKV1BITkdSOFk Previous weeks' work packages will be PDF'd with their comments included. Current work packages will be open for comments. Please be sure to read the Document Overview section of the work packet, since it will change from week to week. The newest packet's Document Overview will include not only context for this week's work, but also feedback on how previous comments have influenced the latest work. | Leah Elzinga | - Last week Stacks presented a first look at a first order workflow and outlined a work process for moving forward. Each week, they’ll deliver a work packet by Friday evening that iterates on the previous week. The RM SIG members (and other FOLIO folks) will have time to comment and ask questions on the document in Google Docs. Any comments added by Wednesday will be addressed and incorporated into the next iteration which comes out the following Friday.
- First work packet from Stacks was released end of last week and reviewed this week:
- Acquisitions Data/Work Flows Work Package
- Slideshttps://drive.google.com/drive/folders/0ByKXfvKzMDq-SldKV1BITkdSOFk
- Feedback on the first work packet
- Folks definitely made comments. Ca. 30 comments received on the first packet. No significant dissension, so all was reviewed by Stacks and incorporated.
- It looks like the comments disappeared. That happened when Stacks turned off the commenting at the end of the commenting period. They will make sure that comments are still visible even after commenting is disabled, and all work packets with comments will be archived and accessible.
- If feedback is clear and no point of contention, no need to discuss; will just be incorporated
- If contentious, then will aim to discuss those during the SIG meetings
- Would be nice to be able to print the Google Doc so that it can be reviewed offline (Martina):
- Stacks will check on that and respond.
- Stacks will make sure that anything that needs clarification is discussed in the work package, in the notes
- Make sure feedback is specific to an item seen in the workflow
- Important to look at the text and the diagram together, to make sure you're understanding the flow. Each element in the diagram has a number that corresponds to a number in the text.
- More general comments:
- Kristin Martin and Leah will look at more general comments and work on how to gather those for future discussion/review in the SIG
- Maybe use Discuss for those more general discussions
- Mike Winkler
- Would be good to have a summary recap of the discussions in the weekly SIG meeting
- Also set the context, e.g. we’re in week 2 of an x week process; this is what we expect to cover and what we expect to get to at the end point
- If there’s something you would like to discuss in the meeting, then note that in the Google Doc comment, Stacks will make sure to address in the following week’s meeting
- If there’s a SME you want to be included in the discussion, mention them in the notes, and it will send them an e-mail (@name/e-mail)
- First packet also posted on Discuss, but no comments there
- We'll keep posting on Discuss the next few weeks and see whether any comments happen there.
VERY CRITICAL TO COMMENT ON THE WORK PACKET AS QUICKLY AS POSSIBLE. WORK WILL MOVE FOWARD REGARDLESS, SO IF YOU WANT YOU COMMENTS INCORPORATED, BE SURE TO REVIEW THE WEEKLY WORK PACKETS. - This week's work packet (# 2)
- Packet (add link)
- Slides (add link)https://drive.google.com/drive/folders/0ByKXfvKzMDq-SldKV1BITkdSOFk
- This week’s packet:
- Library is ready to order items, and need to create the order
- Still working on ordering physical monographs, but this portion is smaller and more focused
- Start with PO having been created or not, and whether that PO needs to be sent to the vendor or not
- No swimlanes this week; just focusing on the end user tasks, and just a very specific one this week
- No “happy path” designation this time; now including more options/decision points
- Miscellaneous
- Vendor file & Fund accounting will be part of the Stacks work
- Stacks will not be done after v1; will be planning for additional versions
- Martina: workflows are very complex and different from library to library, workflows need to be linked with each other where it is necessary and convenient to use
- Stacks will provide a list of the workflows that will be covered during development
|