Analyse and implement 'missing' elements in the Instance Record - part 2
Description
Priority
P3Fix versions
Development Team
Assignee
Charlotte WhittSolution Architect
Parent
Parent Field Value
Parent Status
relates to
Checklist
hideTestRail: Results
Activity
Charlotte Whitt January 21, 2019 at 12:01 AM
Hi @cate - is closed with following remarks:
stories re. refinement of edit with use of look up features and two way dependent value selection is moved to UXPROD-1420
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 AMEdited
@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:
Tag this feature with "split"
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)
Move any unfinished stories into the new feature
Mark this feature complete
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!
Details
Details
Reporter
Charlotte WhittAnalysis Estimate
Analysis Estimator
Charlotte WhittFront End Estimate
Front End Estimator
Niels Erik NielsenFront-End Confidence factor
Back End Estimate
Back End Estimator
Niels Erik Nielsen
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