Batch Importer (Bib/Acq)
(UXPROD-47)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Batch Importer (Bib/Acq) |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Ryan Taylor |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | crossrmapps, data-import, post-mvp, round_iv, swag | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Release: | Not Scheduled | ||||||||
| Epic Link: | Batch Importer (Bib/Acq) | ||||||||
| Front End Estimate: | Large < 10 days | ||||||||
| Front End Estimator: | Ivan Kryzhanovskyi | ||||||||
| Front-End Confidence factor: | High | ||||||||
| Back End Estimate: | Large < 10 days | ||||||||
| Back End Estimator: | Kateryna Senchenko | ||||||||
| Estimation Notes and Assumptions: | Estimate assumes 1) no deprecation of existing permissions, 2) no breakdown by record type, 3) include automated tests | ||||||||
| Development Team: | Folijet | ||||||||
| PO Rank: | 80 | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||
| Rank: hbz (TBD): | R4 | ||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||
| Description |
|
As of Lotus release, there are 2 User permissions for Data Import
As of Morning Glory release, there are 5 User permissions for Data Import
Assumptions:
No further work on DI permissions is currently planned. Possible additional future permissions
UI
BE
|
| Comments |
| Comment by Nick Cappadona [ 12/Aug/20 ] |
|
I know permissions have not been a focus just yet but I wanted to share some of our experiences at Cornell. This is in follow up to a thread in the #data-import-batchload channel and the recently merged PR for ui-data-import. Here are the steps taken on snapshot-load earlier today to test ui-data-import#650:
This resulted in an error and I was only able to successfully create a Job Profile after adding the Inventory: All permissions permission to the di_test user. Unable to render embedded object: File (Screen Shot 2020-08-12 at 9.01.18 AM.png) not found. Based on our (incorrect?) understanding of the permissions documentation in stripes-core, a user with the settings.data-import.enabled permission should be allowed to use the entire feature set or functionality presented under Data Import within the settings app. Similarly, based on the documentation, there is an expectation that a user with the module.data-import.enabled permission should be allowed to use all the features of the Data Import app, which is currently not the case. |
| Comment by Ann-Marie Breaux (Inactive) [ 13/Aug/20 ] |
|
Good comments, Nick Cappadona I expect we'll run into something similar once we start working with invoices and orders, such that the user importing acq data will need permissions in the order and invoice apps, and maybe permissions in the finance, receiving, and organizations apps. Definitely something to keep in mind. |
| Comment by Jacquie Samples [ 08/Dec/20 ] |
|
Thanks for explaining the permissions situation Nick Cappadona. We will want to have separate permissions for people creating profiles from scratch, people using existing profiles to "clone" new ones, and for people needing to edit existing profiles. Then, permissions for those allowed to use the Data Import profiles. I am not clear where we are with permissions, but at Duke, we prefer them to be as granular as possible as staff across our institution have differing expertness around the Data Import CRUD functions. That is, some people just need to be able to import records/data which touches on Ann-Marie's Ann-Marie Breaux reflection on Order and Invoice apps, and other acquisitions-related app permissions. |
| Comment by Ann-Marie Breaux (Inactive) [ 08/Dec/20 ] |
|
Hi Jacquie SamplesI attached a draft of the permissions we're planning for data import. Right now, there's only 2 permissions - 1 that allows the user to do anything with the Data Import app, and 1 that allows the user to do anything with the Data Import settings. We are cleaning up the UI names for those 2 permissions in Iris (
|
| Comment by Nick Cappadona [ 08/Dec/20 ] |
|
Jacquie Samples – No worries Ann-Marie Breaux – Thanks for sharing the draft permissions and for the heads up that the cleaned up and simplified data-import app/settings split will be ready for Iris via
|
| Comment by Ann-Marie Breaux (Inactive) [ 10/Dec/20 ] |
|
Updated the attached spreadsheet to include Anne H's findings about importing versus settings permissions |
| Comment by Ann-Marie Breaux (Inactive) [ 09/Feb/22 ] |
|
Reviewed and confirmed estimates in Lotus planning Ivan Kryzhanovskyi Kateryna Senchenko; review and increase confidence after SME mtg |
| Comment by Ann-Marie Breaux (Inactive) [ 11/Feb/22 ] |
|
Jacquie Samples and Nick Cappadona We may be doing some work on permissions in the Morning Glory release. I have completely rewritten the description. Please review and let me know what you think. Jacquie, I know that you said much granularity, but per comments from leeda.adkins@duke.edu at the DI Subgroup meeting, it seems like having the options detailed in the In scope section of the description will suffice for now. If we need to get more granular in the future, and use cases are identified, then we can. |
| Comment by Ann-Marie Breaux (Inactive) [ 11/Feb/22 ] |
|
Kateryna Senchenko and Ivan Kryzhanovskyi I haven't built the stories yet, but see the In scope section of the description. Are you still comfortable with the BE/FE T-shirt sizes? |
| Comment by Kateryna Senchenko [ 11/Feb/22 ] |
|
Hi Ann-Marie Breaux, existing Karate and e-2-e tests will probably need to be updated, some additional tests (for negative scenarios, for example denying ability to delete logs if user lacks necessary permissions) should be added. I'd increase BE estimate to account for additional testing work. Thank you! |
| Comment by Jenn Colt [ 25/Feb/22 ] |
|
In the current Cornell tenant assigning: Data Import: All permissions does not allow people to assign job profiles to jobs, therefore we are having to give everyone DI settings permissions which we don't want to do. Commenting on this here since this issue assumes the current permissions work properly, which I don't think they do. |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Jun/22 ] |
|
Hi Jenn Colt In Morning Glory, there's 3 changes that will help (I think)
All of these are available on Snapshot now, if you would like to test them |