Analyse and implement 'missing' elements in the Instance Record

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

Q3 2018 - Plan as of 9/12/2018:
Following fields that we can implement in detail view and/or edit form as time permits, provided that we release the related branches of mod-inventory-storage and mod-inventory now, something that's still to be decided:

  • HRID

  • Cataloged date

  • Previously held (form only I think)

  • Staff suppress (form only)

  • Suppress from discovery (form only)

  • Publisher role

  • Publication frequency

  • Publication range

  • Electronic access (group of fields)

Priority

Fix versions

Development Team

Prokopovych

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema September 25, 2018 at 11:49 AM

Hi , can you please clean up this feature? Let's move all these open and analysis complete stories into another feature (all the stories linked to this one should be closed by this point, as the release is on Friday). Once you've moved the open stories, we can then close this feature. Thanks!

Charlotte Whitt September 12, 2018 at 10:15 AM

Hi - I like your plan. Let's do it like that. I'll split the issue between Q3 2018 and Q4 2018. Thanks!

Niels Erik Nielsen September 12, 2018 at 9:58 AM
Edited

Wayne will not have time to populate reference tables this week, so fields based on reference tables can not yet be populated and would thus not display (even provided we had the time to implement them UI-wise)

The fields are:

Instance status (and thus 'Date status updated')
Mode of issuance
Cataloging level
Statistical code

Other fields that are not UI or not 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)
Preceeding title

That leaves following fields that we can potentially implement in detail view and/or edit form as time permits, provided that we release the related branches of mod-inventory-storage and mod-inventory now, something that's still to be decided.

HRID
Cataloged date
Previously held (form only I think)
Staff suppress (form only)
Suppress from discovery (form only)
Publisher role
Publication frequency
Publication range
Electronic access (group of fields)

Charlotte Whitt September 11, 2018 at 4:41 PM

@cate - is still working on these stories. I'll update the split or update fix version accordingly to what has been solved/not solved - first thing tomorrow morning (when I have a status from dev's point of view)

Cate Boerema September 11, 2018 at 12:42 PM

, given all the open stories on this feature, I think we can safely assume this is not going to make Q3 2018 release. If some significant part will make the Q3 release, you could split this feature into two (one part for Q3 and the other for Q4). If not, please just change the fix version to Q4.

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 January 18, 2018 at 10:48 PM
Updated September 16, 2020 at 9:12 PM
Resolved September 25, 2018 at 5:17 PM
TestRail: Cases
TestRail: Runs