Priority/Done? | Notes | JiRA ticket /Confluence page |
|
High | VLBA: DA archive tools (note specifically the limitation of USNO data not having PI) - CHECK IF ALL REQUIREMENTS ON CONFLUENCE ARE SATISFIED
- Current tools should be able to add PI for USNO
| |
Med | Wrong band designation in VLBA data (old data only?) | Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7420 |
---|
|
| This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear. |
Med | For observing VLBA projects that incorporate other dishes (e.g. +Y1, +Y27 etc), the VLA files should be associated with the relevant VLBA segment and not considered as "mixed" projects. This has been descoped from ticket proprietary period setter: Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
7185 but needs to be picked up in future AAT releases | New JIRA ticket not yet created. | | The VLBA DA tools for changing PI and setting proprietary period have been complete for some time. The confluence page also mentions a tool for annotations; maybe that part should be moved to the Data Integrity section? |
High | VLBA+EVLA projects without metadata and sometimes also mismatched PI | Med | Default Instrument of VLBA projects in AAT/PPI | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7208 |
---|
|
Confluence req: VLBA: Default Instrument of VLBA projects in AAT/PPI |
|
High (4.2.1) | Proxy issue for huge | Low | Add PTF link in Project View for VLBA projects | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7461 |
---|
|
| Low | |
|
High (4.2.1) | Slow VLBA indexingImport remaining 8 GMVA files | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7438 |
---|
|
| Low | Mark4 files with 0 length getting added to new archive metadata Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
| 7297 | Small number of files affected. | Low | |
|
Med | Wrong band designation in VLBA data (old data only?Incomplete VLBA data of observations crossing midnight (open in case more cases show up) | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-6916 |
---|
|
| Low | | This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear. |
Med | Create USNO download acknowledgement- For observing VLBA projects that incorporate other dishes (e.g. +Y1, +Y27 etc), the VLA files should be associated with the relevant VLBA segment and not considered as "mixed" projects. This has been descoped from ticket
Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
6952 | 4.1.1 | import FITSAIPS files without matching projects (51 files) and project GP0024 | - but needs to be picked up in future AAT releases
| Jira |
---|
Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-74267609 |
---|
|
| Ticket created Anna Kapinska, Emmanuel Momjian, and Anthony Sowinski should check it to make sure it's correct and specifies all requirements.
|
Med | Default Instrument of VLBA projects in AAT/PPI | 4.1.1 | Add FITSAIPS files to new archive and segment association | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
| 7328 | 4.1.1 | And a new ticket created: old VLBA project metadata issues Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7379 |
---|
|
| 4.1.1 | VLBA data structure in the new archive - improved interface |
|
Med | Add PFT (proposal finder tool) link in Project View for VLBA projects | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 7185 |
|
Low | Import remaining 8 GMVA files | Confluence: GUI (segment hierarchy) for VLBA data in the new archive
√ | 877 VLBA correlations with missing files entries | Jira |
---|
server | DMS JIRA |
---|
Jira |
---|
server | DMS JIRA | serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7471 |
---|
|
| √ | proprietary clock for VLBA data | columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 6552 | done | √ | VLBA Reingestion Refinements
| Low | Mark4 files with 0 length getting added to new archive metadata |
Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 5917ongoing → done | √ | | Small number of files affected. |
Low | Incomplete VLBA data of observations crossing midnight (open in case more cases show up) | VLBA Polarization Duplication | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 5640 | done | √ | String Terminators in VLBA fields
|
High | Create USNO download acknowledgement | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 5641 | done |
|
√ | BL473 unlock and missing segments(reopened) Low?
| Remove Legacy Archive label and link from new archive | Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7375 |
---|
|
Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 7148done | √ | VLBA data structure in the new archive | Update (26-Sep-2022, Anna): the link is still present on some of the AAT subpages, especially the download status page when request for data is submitted. The new archive has a link to the legacy archive at the top. This needs to be removed since the legacy archive will not be accessible from outside. |
√ 4.2.0 | Add wget command in emails generated by the AAT upon downloading data | Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7421 |
---|
|
|
|
√ 4.1.1 | import FITSAIPS files without matching projects (51 files) and project GP0024 | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey |
---|
|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7426 |
---|
|
|
|
---|
√ 4.1.1 | Add FITSAIPS files to new archive and segment association | 7076 |
Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7328 |
---|
|
|
|
√ 4.1.1 | old VLBA project metadata issues | 7182 | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7379 |
---|
|
|
|
√ 4.1.1 | VLBA data structure in the new archive - improved interface | Jira | 7183 Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7185 |
---|
|
Confluence: GUI (segment hierarchy) for VLBA data in the new archive |
|
√ (4.1.1) | Database has zeros for min/max frequencies for some archive files | Jira |
---|
server | DMS JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7184 |
---|
|
done |
|
√ | USNO Proprietary Download System/A way to deliver data from projects that are not archived | | done | 877 VLBA correlations with missing files entries | √ | Remove Legacy Archive label and link from new archive | Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA- |
---|
|
| 7375The new archive has a link to the legacy archive at the top. This needs to be removed since the legacy archive will not be accessible from outside. |