...
| Item | Who | Notes |
|---|---|---|
| Minute Taker | Peter McCracken will take notes. | |
FOLIO Codex meeting next week on 7/7, so RM SIG meeting cancelled 7/7 Consideration of schedule in July. Kristin Martin out 7/14 | Kristin Martin | Next week, Codex SIG will take place of RM SIG. The week after, Kristen Wilson will take over as convener, as Kristin Martin will be out. |
Revised version of complete RM Prototype and walk-through of features
| Filip Jakobsen providing update and changes to how information is shared before meetings. Filip shared new prototype site at http://ux.folio.org/prototype/en/users. New structure allows exploration of site. There's a player, at "Watch Demo", which shows demo of each related app. Comment space now included information about UX iterations, on discuss.folio.org. Filip creates new topic on which people can comment on each iteration. Also, designers will create video before each SIGD meeting, and give them time to invite appropriate colleagues. Will hopefully make it possible to include most appropriate individuals more quickly. Will also make SIGS meetings more accessible to those in time zones that don't match well with live meeting. Multilingual prototypes are also available at language picker in lower left corner. Will affect many menus throughout the system, though a few still need to be converted. Will also have voice-overs in other languages. The plan is that any prototype will have a video walkthrough, to make it possible for others to keep up, catch up, and know where the project stands. More apps are available in dropdown menu from arrow at top center, to right of visible app icons. Kristen W asked question about how we connect before meetings – discussion list, slack list, discuss.folio, wiki, etc.? Need to ensure we're getting information about prototypes to attendees. Filip would like folks to link to ux.folio, as you can link to different apps directly; he would like to see people focusing on that site. Sebastian Hammer asked about uploading protoypes. Filip explained that people can upload prototypes themselves; Stacks is working on making this work effectively. Filip and Kevin have been discussing this. Starting this week, Filip will be back to working on the workflows that are relevant to RM. Kristin Delwo responded to question from Lynn Bailey, re need to keep track of what Stacks is doing and what Filip is doing in design work. Need to keep an eye on scoping. K Delwo said Kevin will be contributing in the same manner as Filip is starting to do. | |
| Recommendations for publishing summaries of features discussions | ||
Discussion of orders prototype | Former user (Deleted) | Kevin started presentation on his mockup. K Martin had a problem with her view; Kevin said it's a server caching issue. Kevin did walkthru of current prototype. Simple demo of existing states, items that can be tracked thru interface. Creating ability to change view; sort by columns; modify views, as needed. Plan is to only show tables on larger screens; hard to manage tables in smaller screens. Filip talked about way to turn tables in to cards on a small screen. Kevin said this is doable through preferences choice. "Orders", "Serials", "Subscriptions" types at present. Showed Preferences Configuration page, with orders layout; default configuration should be able to modify based on screen type/size. What's displayed here is not yet in Filip's demo, but is up at folio.stacksdiscovery.com. Will be moved into Filip's prototype tool next week. Information shown on sample order form, where vendor, funds, notes, etc. can be incorporated to task. Also, "related tasks". Walked thru example of ordering process for items, serials, subscription. Later, K Delwo clarified that some of this might take some time, depending on speed going in each project. S Hammer highlighted importance of sticking to design plans laid out within Stripes guidelines. Standard behavior between apps and among modules is making FOLIO look v encouraging. Seb suggested that try to develop a variation of display that leans on existing behavior of prototypes - vertical panes, drilling down, etc. Important to keep consistency through development and design. Also, he sees 'card' metaphor really useful in other apps, perhaps. Perhaps use card-style display through multiple apps. "Serial" means single title; "Subscription" will be packages. Full API connection with order options is likely not v1, but will be looking to do read-only APIs, rather than push/pull APIs at very start. K Martin pointed out prior discussion about various order types, which would be useful for Stacks team to review as they put these structures into place. K Delwo said as content is published in next week or two, they'll address used terminology; this will also be a good place to put in comments about terminology, usage, etc. K Martin pointed out importance of search box for a vendor beyond just a drop-down box. Same for funds. There are hundreds and hundreds of vendors and funds at large institutions. K Delwo asked about possible default short list of funds or vendors - perhaps by format? K Wilson suggested "recently used" or "frequently used". V Martin, said most of people at Duke only order from specific funds, so defaults there would be good. Only occasionally do they order from other funds. K Martin asked about encumbrance and payment information; not shown in workflow. Asked for clarity on some of the financial issues. K Delwo said she's talked a lot with Leah about specifics, and that they're working through specific details to understand them best before putting them into the prototype structure. Much work is going on with many different scenarios; they just need to be defined and clarified before building structure for this in prototype. Similarly, K Martin asked a bit about order hierarchy; lines etc., associated with each order. K Delwo would like to publish to Google Drive to get discussion and feedback before meetings.
|
| Review of configuration for v1 | Leah shared Acq v.1 Scope of Work presentation. Leah is project mgr and analyst at Stacks. Team has been analyzing tools, is trying to define scope for v1. Determine which items need immediate attention; which can be delayed. Items to be included in v1:
|