Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Below is a list of items that are priorities for Archive implementation, some of these are Legacy AAT retirement tickets, others are new development. The order in the tables is in priority order.


Main topics (click link to jump to section in page):

Data Delivery

Search/Data Selection

VLBA-specific

VLA(VLBA) Metadata presentation

Legacy VLA Data

Data Integrity

DA Tools

Missing Data

Other

ALMA

Product Versioning



Data Delivery

Anchor
DataDelivery
DataDelivery

 Scriptable Query Interface to NRAO Archive
Priority/Done?NotesJiRA ticket /Confluence page
CriticalDownloads via Scriptable query interface

Scriptable Query Interface to NRAO Archive  

SSA7421Put warning that only one CMS at a time can be requested in AATSSA7106Bulk download of Calibration tarballs7353
critical (4.2.0)The email sent by the archive tool will include the wget command in the near future.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
key

WS-

1395


criticalA friendly error is needed when a users is not authorized to access proprietary data.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7474

confusing to staff as well

-need to kill RH, WS 3.0+

medium
criticalRestore data using same version of CASA as calibrated

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
key

WS-1405


mediumPut warning that only one CMS at a time can be requested in AATcould be a flyover text (currently has a flyover circle with slash)for pipelineoption to return UNTAR'd file does not work 
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
6495https://open-confluence.nrao.edu/display/SRDP/Product+lists+for+Basic+and+Calibrated+Measurement+Set+downloads
pipeline topic
7106


could be a flyover text (currently has a flyover circle with slash)
high (WS 2.8/2.9)high

Clean up the nested directory data delivery mess


legacy VLA data deliveries are one level deeper in directories than an SDM

*May need revisions to account for VLBA differences.

Delivery Directory Improvements

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7000

WS 2.7 or 3.0?
attempted for planned 4.2.0 but is deferred2

Don't restrict download number limit.

New ticket to remove the '/100 string from webpage'

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7352
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7436

We would like no limit on the number of files, but keep the 10TB for the total downloaded volume.
4.2.1

Fix select-all functionality

  • Always have select all available (only displayed files/SDM or from all pages)


  • make select-all work properly with select/deselect
NEW TICKETmediumDownload weblogs directly (and/or serve them as well!)Direct weblog download from archive search return interfacemedium

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7573

lowarchive should ask for confirmation to continue if the download or processing job is considered largeTo be requestedThe front end can show size estimates for various products.

mediumDownload weblogs directly (and/or serve them as well!)lowData Delivery times out if tar file(s) are too large/time consuming

Direct weblog download from archive search return interface 

issuekey,summary,issuetype,created,
will not be an issue with taring not being the default.lowarchive-new delivery not chmod'd/chowned

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
key

SSA-6083

WS-1388

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keyWS-1389
!


mediumBulk download of Calibration tarballsSSA-5096open up local delivery restrictions (to /home and /lustre). 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7179
The part related to opening the download destination to nm-### accounts on lustre is
7353


lowarchive should ask for confirmation to continue if the download or processing job is considered largeTo be requestedThe front end can show size estimates for various products.
lowData Delivery times out if tar file(s) are too large/time consuming


Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7345
This should cover users with visitor accounts wanting to download data to lustre, and local staff wanting to download data to their local machines. We have a problem with the quota of the observer accounts (I downloaded 8 TB of data to my observer account!); CIS remains irresponsive!
columnIdsissuekey,summary,issuetype,created,
disable checksums by default
Jira
serverDMS JIRA
columnIds
updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7343
6083
will not be an issue with taring not being the default.
lowarchive-new delivery not chmod'd/chownedmake tar downloads default to 'off'


Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7344

Search interface/Data Selection

5096

√ 2022.2 pipelineoption to return UNTAR'd file does not work 
Priority/Done?NoteshighScriptable query interface

Jira
serverDMS JIRA

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01keySSA-7395

columnIdsissuekey,summary,issuetype,created,updated,

high

Fix Frequency-dependent FOV and position searches

  • exact same feature as legacy archive, must select to do the freq. dependent FOV
  • legacy archive has this feature
JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,

duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

4915
pipeline topic
√ (4.2.0)The email sent by the archive tool will include the wget command in the near future.

 

Jira
serverDMS JIRA
serverIdeb2e750b-a83a

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdeb2e750b-a83a

-387e-8345-36eee8a98f01
keySSA-

7497

7421

high

Position searches provide distance from searched position and sort by distance

  • legacy archive feature
User request, but is a legacy AAT featuremedium

Treat wild cards consistently in AAT search interface

  • account for * in source names

open up local delivery restrictions (to /home and /lustre). 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7387issuekey

7179

The part related to opening the download destination to nm-### accounts on lustre is

Jira
serverDMS JIRA

columnIds

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7345

This should cover users with visitor accounts wanting to download data to lustre, and local staff wanting to download data to their local machines. We have a problem with the quota of the observer accounts (I downloaded 8 TB of data to my observer account!); CIS remains irresponsive!
disable checksums by default

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7496

7343

low

make tar downloads default to 'off'
Allow search return of observation scans?

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7344



Search interface/Data Selection

Anchor
Search
Search

7388
Priority/Done?Notes

high

Fix Frequency-dependent FOV and position searches

  • exact same feature as legacy archive, must select to do the freq. dependent FOV
  • legacy archive has this feature

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,

Helpdesk ticket for a search return we do not have in AAT, but legacy archive provides.

high

Allow search filtering based on total time on source.

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7424

Based on legacy archive helpdisk question from user. UC feedback as well.

4915
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,

mediumFix mosaic position searches for VLASS and ALMA mosaics (subscan vs. scan)Rearrange boxes in 'Search Inputs'Ticket to be created.

Download number limit: 100 data sets, but download data volume limit to 10TB per request.

Doesn't fully solve problem see also

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7352

This change has already been made by Stephan, but 100 files is too limiting for various cases (take BM360 as one example). We would more likely want no limit on the number of files, but keep the 10TB for the total downloaded volume.

VLBA Stuff

issuekey,summary,issuetype,created,updated,duedate

7497


high (4.2.2)

Position searches provide distance from searched position and sort by distance

  • legacy archive feature
Priority/Done?NotesJiRA ticket /Confluence pageHighAdd wget command in emails generated by the AAT upon downloading data

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7421

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

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due

https://open-confluence.nrao.edu/display/SPR/VLBA%3A+DA+archive+tools

proprietary period setter: 

Jira
serverDMS JIRA
columnIds
,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdeb2e750b
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7350

needs follow up, some things are inconsistent (especially the topic of the tool's readiness to change the proprietary period of VLBA data).HighVLBA+EVLA projects without metadata and sometimes also mismatched PI

7387

User request, but is a legacy AAT featuremedium

Treat wild cards consistently in AAT search interface

  • account for * in source names

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7423

7496

High
lowAllow search return of observation scans?Proxy issue for huge VLBA projects

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-74367388

Helpdesk ticket for a search return we do not have in AAT, but legacy archive provides.

high

Allow search filtering based on total time on source.

MedWrong band designation in VLBA data (old data only?)

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7420

This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear.

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7424

Based on legacy archive helpdisk question from user. UC feedback as well.mediumFix mosaic position searches for VLASS and ALMA mosaics (subscan vs. scan)MedFor 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
key

SSA-7185 but needs to be picked up in future AAT releases
New JIRA ticket not yet created.

WS-1365



Rearrange boxes in 'Search Inputs'Ticket to be created.
√ (4.2.0)Scriptable query interface

Scriptable Query Interface to NRAO Archive

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7395


Download number limit: 100 data sets, but download data volume limit to 10TB per request.


Doesn't fully solve problem see also

MedDefault Instrument of VLBA projects in AAT/PPI

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7208

Confluence req: VLBA: Default Instrument of VLBA projects in AAT/PPI

MedAdd PFT (proposal finder tool) link in Project View for VLBA projects

7352


This change has already been made by Stephan, but 100 files is too limiting for various cases (take BM360 as one example). We would more likely want no limit on the number of files, but keep the 10TB for the total downloaded volume.


VLBA Stuff

Anchor
VLBA
VLBA

key,summary,type,created,updated,due
Priority/Done?NotesJiRA 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

https://open-confluence.nrao.edu/display/SPR/VLBA%3A+DA+archive+tools

proprietary period setter: 

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns
,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7461
7350

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?

HighVLBA+EVLA projects without metadata and sometimes also mismatched PILowImport remaining 8 GMVA files

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-74387423


High (4.2.1)Proxy issue for huge VLBA projectsLowMark4 files with 0 length getting added to new archive metadata

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-
7297

Small number of files affected.

7436


High (4.2.1)Slow VLBA indexingLowIncomplete VLBA data of observations crossing midnight (open in case more cases show up)

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-6916

HighCreate USNO download acknowledgement

7563
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-6952

√ 4.1.1

7541


MedWrong band designation in VLBA data (old data only?)import FITSAIPS files without matching projects (51 files) and project GP0024

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7426

√ 4.1.1

7420

This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear.MedAdd FITSAIPS files to new archive and segment association
  • 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
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySSA-
7328
√ 4.1.1old VLBA project metadata issues
  • 7185
    but needs to be picked up in future AAT releases

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7379

√ 4.1.1

7609

Ticket created Anna Kapinska, Emmanuel Momjian, and Anthony Sowinski should check it to make sure it's correct and specifies all requirements.


MedDefault Instrument of VLBA projects in AAT/PPIVLBA data structure in the new archive - improved interface

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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7185

7208

And a new ticket created:

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7619

Confluence req: VLBA: Default Instrument of VLBA projects in AAT/PPI


MedAdd PFT (proposal finder tool) link in Project View for VLBA projects7277877 VLBA correlations with missing files entries

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7471

proprietary clock for VLBA data JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

6552

7461

doneVLBA Reingestion Refinements
LowImport remaining 8 GMVA files

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

5917

7438

ongoing → doneVLBA Polarization Duplication
LowMark4 files with 0 length getting added to new archive metadata

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

5640

7297

Small number of files affected.LowIncomplete VLBA data of observations crossing midnight (open in case more cases show up)doneString Terminators in VLBA fields

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

5641

6916

done
HighCreate USNO download acknowledgementBL473 unlock and missing segments

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7148

6952

done
VLBA data structure in the (reopened) Low?
Remove Legacy Archive label and link from new archive

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7375

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7076 JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

7627

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.0Add wget command in emails generated by the AAT upon downloading data

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7182

7421


√ 4.1.1

import FITSAIPS files without matching projects (51 files) and project GP0024

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7426


√ 4.1.1

Add FITSAIPS files to new archive and segment association

7183

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7184done

7328


USNO Proprietary Download System/A way to deliver data from projects that are not archiveddone4.1.1old VLBA project metadata issues

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

Remove Legacy Archive label and link from new archive JiraserverDMS JIRA

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

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.

VLA Metadata Presentation

7188 https://open-confluence.nrao.edu/display/SRDP/VLA+Metadata+Display+Updates

JT: revise to capture what we want about the frequency/setup information

Incorrect metadata sometimes displayed for projects with duplicate proposal IDs between VLA and VLBA7318Subscans table holding both Radian and Degree positions5275archive search returning incorrect projects6192

7379


√ 4.1.1VLBA data structure in the new archive - improved interfacePriority/Done?NotesJiRA ticket /Confluence pageCriticalMake scanlist information useful 

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-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
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

This ticket has multiple points to make the new tool match the Legacy archive and to have the displayed data be much more useful.
HighVLA Metadata display updates. https://open-confluence.nrao.edu/display/SRDP/VLA+Metadata+Display+UpdatesThis has many items including 'telescope observing logs'.

7277


877 VLBA correlations with missing files entries

Jira
serverDMS JIRA
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7471


proprietary clock for VLBA dataMedium

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

6552

done
MediumVLA/VLBA proposal code degeneracyVLBA Reingestion Refinements

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

5538

5917

ongoing → done
VLBA Polarization Duplication

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-73185640

done
String Terminators in VLBA fieldsMediumIndexing of VLA low band projects

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-71875641

done
BL473 unlock and missing segments

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7148

done
VLBA data structure in the new archive

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

done

Legacy VLA Data

Priority/Done?NotesJiRA ticket /Confluence pageHighMetadata Issues in Legacy VLA data

7076
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7192

Needs input from BryanHighLegacy VLA data missing error codes in the new archive toolHighmetadata errors in VLBA (BD114) and old VLA data in new archive
Jira
serverDMS JIRA
columnIds
7182
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7191

Mapping of quality errors were lost. Stephan will continue following up with Bryan. Blocker for LA retirement.

7183
Jira
serverDMS JIRA
columnIds

issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-

7128

jira
7184

doneserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnsUSNO Proprietary Download System/A way to deliver data from projects that are not archiveddone