[DAMD-57] Implement range of datamodel changes Created: 14/May/19  Updated: 24/May/19  Resolved: 24/May/19

Status: Done
Project: Data Model
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Normal
Reporter: hassan Assignee: hassan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by DAMD-42 Reconsider the details of the pfsConf... Done
is blocked by DAMD-8 Object IDs need to be 64bits, so 16 h... Done
is blocked by DAMD-49 Clarify use of expId Done
is blocked by DAMD-53 PfsObject filename format: change nVi... Done
is blocked by DAMD-54 Align PfsCoadd and internal PfsObject... Done
is blocked by DAMD-55 Change catId formatting from %3d to %03d Done
is blocked by DAMD-56 Change pfsVisitHash formatting from %... Done
Story Points: 1
Reviewers: price

 Description   

There are a number of relatively minor changes in the datamodel that when put together are significant. These are tracked as separate JIRA tickets (see linked tickets below). To minimize confusion to users, these all will be merged to master in one action. This ticket encompasses this activity, and provides a name for a 'staging' branch for which the merging of the individual tickets will be done, prior to a single merge to master.

Firstly, a ticket branch corresponding to this ticket will be created (call this Branch S). Then the branches for the individual tickets will be merged to Branch S. Finally, Branch S will be merged to master.

 Comments   
Comment by hassan [ 24/May/19 ]

Merged to master (commit 60d300c)

Generated at Sat Feb 10 15:33:47 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.