Analyse and implement 'missing' elements in the Instance Record - part 2

Description

Analyse and implement 'missing' elements in the Instance Record - input from MM-SIG working groups

Source: https://discuss.folio.org/t/codex-metadata-analysis-when-should-a-new-instance-be-created/1001

https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439

Q4 2018 - Plan as of 9/12/2018:
The fields are:

  • Instance status (and thus 'Date status updated')

  • Mode of issuance

  • Cataloging level

  • Statistical code

Other fields that didn't make it with the Q3 2018 release () to be UI or UI ready:

  • Index title (present in back-end but will not be UI visible and is not yet populated)

  • Succeeding title (we may have the structure for that, but could be a design decision to make) -> UIIN-426

  • Preceeding title -> UIIN-426

Priority

Fix versions

Development Team

Prokopovych

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte Whitt January 21, 2019 at 12:01 AM

Hi @cate - is closed with following remarks:

  1. stories re. refinement of edit with use of look up features and two way dependent value selection is moved to UXPROD-1420

  2. UX refinements, e.g. UIIN-364 on display of supplemental data from reference tables for three Instance fields in the Administrative accordion, is moved to

Charlotte Whitt January 14, 2019 at 11:25 AM
Edited

@Cate, okay.

I'll move the further refinements as look-up feature, and new component dependent values in the edit form (e.g. statical code types and statistical codes, contributor term and contributor code) as part of the existing UXPROD-1420 for refinements.

Cate Boerema January 11, 2019 at 12:33 PM

Hi , it's end of quarter and this feature looks incomplete. I think you will need to split it:

  1. Tag this feature with "split"

  2. Create a new feature for the unfinished work and make a note at the top of the feature that it was split out from this one (this was requested by the early implementers)

  3. Move any unfinished stories into the new feature

  4. Mark this feature complete

  5. Make a note explaining what was split out in the weekly status report: https://folio-org.atlassian.net/wiki/display/PC/FOLIO+Q4+2018+Weekly+Status+Report

Thanks!

Cate Boerema September 27, 2018 at 10:23 AM

, I'm speaking with Charlotte right now and she suggested the estimates might be lower now that work has already been completed. Could you please re-estimate, if applicable? Thanks!

Done

Details

Reporter

Analysis Estimate

Medium < 5 days

Analysis Estimator

Front End Estimate

Medium < 5 days

Front End Estimator

Front-End Confidence factor

Medium

Back End Estimate

Medium < 5 days

Back End Estimator

Rank: 5Colleges (Full Jul 2021)

R2

Rank: Cornell (Full Sum 2021)

R1

Rank: Chalmers (Impl Aut 2019)

R1

Rank: BNCF (MVP Feb 2020)

R1

Rank: GBV (MVP Sum 2020)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R1

Rank: U of AL (MVP Oct 2020)

R4

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 12, 2018 at 10:24 AM
Updated September 16, 2020 at 9:05 PM
Resolved January 21, 2019 at 12:04 AM
TestRail: Cases
TestRail: Runs