You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 21
Next »
Attendees (please add your name):
Magda Zacharska leeda.adkins@duke.edu Jennifer Eustis Amanda Ros Autumn Faulkner Donald Depoorter Christine Tobias (OLD ACCOUNT) Erin Nettifee Sara Colglazier Jenn Colt Thomas Trutt Erin Weller Scott Perry gongd@msu.edu Kimie Kester
Note taker:
Robert Scheier
Meeting Recording:
Discussion:
Topic | Notes |
---|
Housekeeping - Please add your name to the attendees list
- Please state your name while joining the conversation
| - Mada: Let's start with the housekeeping. Please add your name to the attendees list. And please state your name when joining the conversation so it's easier for Bob when he's taking notes.
|
Development updates | - Magda: The development status, there is not much information on this because we are now mixing Lotus and Morning Glory builds.
- Magda: We have added radio buttons instead of checkboxes. There is a bug. the drop-down should default to "select record identifier." it should not default to barcode. Uploading the barcode file does not work just yet.
- Magda: We get an error message when trying to upload barcodes.
- Magda: We are working on that. There is some progress on the backend, but this is not visible to the UI. So please continue to be patient.
- Magda: On the Scrum Board, you can see there is a lot of other issues. There is progress for items, mostly on the backend. And front-end developers are working on addressing bugfest issues.
- Magda: And this is the work on the backend on issues of displaying records and saving them.
|
Action menu - support for in-app and CSV approach - continue the discussion to review the behavior when both in-app an CSV approach are enabled. | - Magda: The main part of the meeting today, I would like to return to our discussion from the last meeting about the behavior of the action menu, depending on the permissions that they use has. Their permissions will differ between the in-app and CSV approach. After that, I would like to walk again through user records in the in-app approach. I would like to get your feedback on priorities for the next steps. I would like to go back to our conversation regarding the apps with bug edit capabilities that we touched on. Erin mentioned that none of them are actually apps. We will need to either rename them or the options in the accordion. If time permits we will get to the pilot project UIT.
- Magda: So let me start the presentation. I'll start with a quick review of what we discussed last time. So we talk about the permissions that were introduced in Lotus, which was separate for edit, view, and delete.
- Magda: And depending on the permissions you had, the behavior of the action menu, once you open the application and you have a CSV type of permission. You could see right away--start bug edit. Even before the preview was populated.
- Magda: Once the preview was populated, you could download the matched errors or start bulk edit. And if the error accordion was populated, you would have the additional options of download errors in CSV format.
Magda: Please feel free to interrupt me at any moment, if you have an additional question. Magda: And this is the last screen for a CSV approach. Once the edit has been completed we see the completed process and you can start another by uploading another CSV file. So this is how it works in Lotus.
NOTES ARE NOT COMPLETED YET. STILL WORKING ON THEM... |
Bulk edit - user records - in-app approach |
|
Revisit naming convention for Apps with bulk edit capabilities accordion
|
|
Pilot Project UAT | |
Future discussion topic (time permitting): Bulk Edit of the linked records Scheduling edits
|
|
| C |