Added back to grooming because my comment from last time was ambiguous - behavior should be fixed means 1) it needs to be fixed, but hasn't been or 2) it has already been fixed and just needs checking?
Overview: For reporting it would be convenient if the instance HRID were stored as an External ID in every version of the SRS record. Currently this is not the case. When querying the underlying DB, then it shows, that the instance HRID is only populated for the first version, and then not populated (showing as NULL) for every later versions of the SRS record:
Having the Instance HRID populated for each version of the SRS MARC Bib record would be very useful not just for reporting purpose, but eventually also for the Change Record Manager App.
A new version of the SRS MARC Bib is created when doing some updates of the Instance; e.g.
- when adding a Statistical code to an instance with source = MARC by using Inventory Edit, the SRS record is not affected
- when adding a Statistical code to an instance with source = MARC by using Data Import (via an Update Instance action), a new version of the SRS MARC Bib is created
- when editing the Suppress from discovery checkbox by using Inventory edit, a new SRS MARC is created, since that value is stored in the SRS record (but outside of the MARC record itself)
Back ground information:
In the UI the instance HRID seems to be carried over by the UI grabs the instance HRID from the first version of the record.
abreaux - you can probably much better clarify the current data model and the use of a kind of normalization where SRS only store the first version of the HRID.
Please note: the description above is based on what we can see in the UI and in the DB.