Inventory (UXPROD-785)

[UXPROD-972] Wrap up implementation of beta metadata element - create a Instance record Created: 26/Jun/18  Updated: 16/Sep/20  Resolved: 29/Jun/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: inventory, metadatamanagement, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Edit_Instance_full_0810.png     PNG File Edit_holdings_full_0810.png     PNG File Edit_item_0810.png    
Issue links:
Relates
relates to UIIN-363 Refine Display of edit mode (Instance... Closed
relates to UIIN-364 Display supplemental data from refere... Closed
relates to UIIN-404 Instance record, accordion Classifica... Closed
relates to UIIN-150 Settings page. Inventory > Instances ... Closed
relates to UIIN-200 Implement Refined UX design for User ... Closed
relates to UIIN-201 Implement Refined UX design for User ... Closed
relates to UIIN-202 Implement Refined UX design for User ... Closed
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Small < 3 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Medium
Back End Estimate: Small < 3 days
Back End Estimator: Niels Erik Nielsen
Estimation Notes and Assumptions: There are some reference tables for Instances, and for Items to be implemented, and more work can evolve
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R2
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: Wrap up the work on implementation of beta metadata elements in the instance record:

Outstanding tasks (moved to UXPROD-1420):

  • Implement new element: Nature of content
  • Settings page. Inventory > Instances > Nature of content P3 - low priority level, item will be considered for inclusion in the next dev cycle OPEN
  • Settings page. Inventory > Instances > Resource identifier type
  • Settings page. Inventory > Instances > Classification identifier types
  • Settings page. Inventory > Instances > Mode of issuance types
  • Implement Index title as primary key for Result list


 Comments   
Comment by Cate Boerema (Inactive) [ 04/Sep/18 ]

Hi Charlotte Whitt. I am trying to get some of the UXPROD feature status values updated and, looking at the stories linked here, it doesn't seem like development is underway (which is what the "In Progress" status value now represents). Should we change the status to "Analysis Complete" to indicate the stories are written and ready for development?

Comment by Charlotte Whitt [ 04/Sep/18 ]

Hi Cate Boerema, agree. Just change the status. Niels Erik Nielsen Jakub Skoczen and I still expect manual creation of the instance record with all the new elements etc. to be implemented by Q3 2018. BUT edit of holdings and item will be for release Q4 2018.

The container/package record in Inventory is also defined, but I don't know if this is to be developed for Q4 2018 - let's discuss this on Slack (with Hkaplanian Khalilah Gambrell Jakub Skoczen Niels Erik Nielsen)

Comment by Cate Boerema (Inactive) [ 10/Sep/18 ]

Niels Erik Gilvad Nielsen Jakub Skoczen and I still expect manual creation of the instance record with all the new elements etc. to be implemented by Q3 2018. BUT edit of holdings and item will be for release Q4 2018.

Hi Charlotte Whitt. Do you really expect UIIN-200 Closed in the Q3 release? Based on the Open status, it doesn't look like development has even begun. I think you probably ought to just change this entire feature to Q4 at this point.

BTW, I see that UIIN-200 Closed has been assigned to Niels Erik Nielsen but hasn't be assigned to a sprint. This is a really bad state for a story to be in, as it means it won't show up in the Core team unassigned backlog or the sprint backlog. This means it won't come up in any roundup meetings and is very likely to fall through the cracks. Please make sure you don't assign issues to developers without also assigning a sprint.

Comment by Charlotte Whitt [ 10/Sep/18 ]

Hi Cate Boerema - Niels Erik is working on UIIN-223 Closed , UIIN-224 Closed , UIIN-225 Closed , UIIN-226 Closed , UIIN-227 Closed , UIIN-228 Closed , UIIN-229 Closed , UIIN-230 Closed and UIIN-231 Blocked - and his plan is to implement display but also create, clone and update - see MODINVSTOR-152 Closed . But let me follow up on this - if Niels Erik Nielsen advice us to change the realease to Q4 2018.

I get a little worried that lately a couple of my stories seems not even on a sprint. We investigated UIIN-204 Closed last week, and now UIIN-200 Closed .
Cate Boerema Jakub Skoczen - not sure why my stories don't figure on the Core teams backlog, or what might happening here.
Please let me know, if you want me to assign stories to sprints, while writing them - or how we better can prevent these things to happen.

Comment by Cate Boerema (Inactive) [ 10/Sep/18 ]

Charlotte Whitt, the process is for you to write stories and leave them unassigned with no sprint label. You then show up at sprint commit meeting at the beginning of the sprint and advocate for your top priorities to be assigned to the sprint. Jakub Skoczen will then assign them to a developer and apply the sprint tag. Then, at the other roundup meetings (on Thursdays and Mondays), if someone is looking for work, you can again, advocate for your priority stories to be assigned. Make sure you apply the correct priorities in JIRA as developers will sometimes review the Core team unassigned backlog and look for stories and bugs to pick up. If yours are there and properly prioritized, they are much more likely to be worked on. Core team unassigned backlog: https://folio-org.atlassian.net/issues/?filter=10639

You can also agree with a developer that they can pick up a story or bug outside of the meetings, but I think you should let the developer confirm they can handle the story and let them actually do the assignment (assignee and sprint).

The other thing you should pay attention to is issue status. In my experience, it doesn't really matter what someone has committed to in a Slack channel or email thread, if the issue is still sitting in JIRA as "Open" development is probably not happening.

I am sure Jakub Skoczen and Niels Erik Nielsen will jump in if they see it differently. Thanks!

Comment by Charlotte Whitt [ 02/Oct/18 ]

Hi Cate Boerema - update of the edit view of the instance records is done in parallel with updating the detailed view, reorder elements and implementing missing elements. We can't have an edit page which is not in sync with the detailed view. This story I suggest we keep on the Q4 2018 release.

Comment by Cate Boerema (Inactive) [ 02/Oct/18 ]

Thanks Charlotte Whitt, I understand your perspective, but there is no way we can fit an additional 10/10 into the Q4 release. If you want to bring this into Q4, you'll need to pull something out to make room. Sorry!

Comment by Charlotte Whitt [ 02/Oct/18 ]

Okay - let me talk with Niels Erik Nielsen and hear how much time he will estimate remain on updating the edit form of the instance record.

Comment by Charlotte Whitt [ 11/Dec/18 ]

Hi Cate Boerema - what is left to do on this story are some minor work, all "ui-only". I have tagged this story with the "ui-only" label. And will follow up on this, writing explicit stories for, what is missing, so it's easy for other that Niels Erik Nielsen to pick up the work.

Comment by Cate Boerema (Inactive) [ 12/Dec/18 ]

Hi Cate Boerema - what is left to do on this story are some minor work, all "ui-only". I have tagged this story with the "ui-only" label. And will follow up on this, writing explicit stories for, what is missing, so it's easy for other that Niels Erik Gilvad Nielsen to pick up the work.

Thanks Charlotte Whitt. It's really good to have a backlog of ui-only stories for the frontend guys to pull from when they have time. Please tag the stories as ui-only, as well. Since the feature is not targeted for Q1, let's leave the priority at P3. Still, I think there is still a good chance the work will get done even if they are marked P3 - we just need to make sure we address the Q1 features first.

Comment by Cate Boerema (Inactive) [ 22/Mar/19 ]

Removing all but the essential features from the Q2 2019 Core Functional team backlog. After we've run the estimates through the cap plan, we may find we can pull in more.

Comment by Cate Boerema (Inactive) [ 25/Apr/19 ]

Hi Charlotte Whitt, it keeps throwing me off that this is marked "In progress" when it is not being worked on or in scope for the current quarter. About half of this is done - when was it completed? Can we split off the unfinished stuff into a separate feature and mark that Analysis Complete and then mark this Closed? Thanks

Comment by Charlotte Whitt [ 25/Apr/19 ]

Hi Cate Boerema - I can do that - and call this feature part one, and the new one part two.
I recommend we keep the library rankings in the follow up feature (part 2). The work on the instance record, need to be wrapped up (to be done) - as spec'ed by the MM-SIG.

Comment by Charlotte Whitt [ 13/Jun/19 ]

Hi @cate - Why has this feature been set to Draft. The work is in progress. And not much is missing. A few elements, and a couple of reference tables. This work should be done in Q3 2019. For the libraries migrating data into their Sandbox environments

Generated at Fri Feb 09 00:11:53 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.