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 (aside from VLBA at the moment).

Data Delivery

.


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

Priority/Done?NotesJiRA ticket /Confluence page
CriticalDownloads via Scriptable query interfaceThe email sent by the archive tool will include the wget command in the near future.

 

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

Jira
server

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

DMS 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

WS-

7474Put warning that only one CMS at a time can be requested in AAT

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-

7106could be a flyover text

Clean up the nested directory data delivery mess

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

Delivery Directory Improvements

7474

confusing to staff as well

-need to kill RH, WS 3.0+

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

SSA

WS-

7000attempted for 4.2.0 but is deferredDon't restrict download number limit.

1405


mediumPut warning that only one CMS at a time can be requested in AAT
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-
7352We would like no limit on the number of files, but keep the 10TB for the total downloaded volume.Download weblogs directly (and/or serve them as well!)Direct weblog download from archive search return interfaceBulk download of Calibration tarballs
7106


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

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.

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-

7353archive 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.

7000

WS 2.7 or 3.0?
planned 4.2.2

Don't restrict download number limit.

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

Data Delivery times out if tar file(s) are too large/time consuming

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-

6083will not be an issue with taring not being the default.archive-new delivery not chmod'd/chowned

7352

Jiraserver

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-

5096option to return UNTAR'd file does not work 

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

Jira
server

DMS 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+downloadspipeline topic4.1.1

7573


mediumDownload weblogs directly (and/or serve them as well!)
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
key

SSA

WS-

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

1388

Jira
serverDMS JIRA

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01keySSA-7345This 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,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due

4.1.1disable checksums by default JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate

,assignee,reporter,priority,status,resolution

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdeb2e750b

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

SSA

WS-

7343

1389
!


mediumBulk download of Calibration tarballs
4.1.1make tar downloads default to 'off'Priority/Done?NotesScriptable query interface

Scriptable Query Interface to NRAO Archive

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

Fix Frequency-dependent FOV and position searches

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

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
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-
4915
6083
will not be an issue with taring not being the default.
lowarchive-new delivery not chmod'd/chowned


Jira
serverDMS
JiraserverDMS
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-
7497Position searches provide distance from searched position
5096

√ 2022.2 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-

7387User request, but is a legacy AAT featureTreat wild cards consistently in AAT search interface
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-387e-8345-36eee8a98f01
keySSA-7421


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-

7496Allow search return of observation scans?

7179

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

Jira
serverDMS JIRA

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

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

7388

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

Allow search filtering based on integration time.

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-

7424Based on legacy archive helpdisk question from user.

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

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

7343


make 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

Anchor
Search
Search

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,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
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-7497


high (4.2.2)

Position searches provide distance from searched position and sort by distance

  • legacy archive feature

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-7387

User request, but is a legacy AAT feature
medium

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-7496


lowAllow 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-7388

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.
mediumFix mosaic position searches for VLASS and ALMA mosaics (subscan vs. scan)

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-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

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

Anchor
VLBA
VLBA

-8345-36eee8a98f01Add wget command in emails generated by the AAT upon downloading 7421877 VLBA correlations with missing files entriesMark4 files with 0 length getting added to new archive metadata
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,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-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 PI

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


High (4.2.1)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-7436


High (4.2.1)Slow VLBA indexing

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-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-7541


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.
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 
    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
    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-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/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

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 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-7461


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-7438


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-7297

Small number of files affected.
LowIncomplete 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

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


(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-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-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

Priority/Done?NotesJiRA ticket /Confluence page

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
7328


√ 4.1.1old VLBA project metadata issuesAdd FITSAIPS files to new archive and segment association

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.1VLBA data structure in the new archive - improved interface

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
keySSA-7328
old 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
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7277


877 VLBA correlations with missing files entries7379Wrong 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.

7471


proprietary clock for VLBA 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-

6552

done
VLBA Reingestion RefinementsFor 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-

7185 but needs to be picked up in future AAT releases

5917

ongoing → done
VLBA Polarization Duplication

Jira
serverDMS JIRA

serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySSA-7471
VLBA data structure in the new archive - improved interface

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

Confluence: GUI (segment hierarchy) for VLBA data in the new archive

5640

done
String Terminators in VLBA fieldsDefault 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

-8345-36eee8a98f01
keySSA-5641

done
BL473 unlock and missing segmentsVLBA: DA archive tools (note specifically the limitation of USNO data not having PI)

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

proprietary period setter: 

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
-7350

needs follow up, somethings are inconsistent (especially the topic of the tool's readiness to change the proprietary period of VLBA data).

-7148

done
VLBA data structure in the new archiveproprietary clock for VLBA 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-6552

should have been done for 4.1.0. Stephan will follow up to confirm.VLBA Reingestion Refinements

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-5917

ongoingSmall number of files affected.Incomplete VLBA data of observations crossing midnight (open in case more cases show up)

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
key

SSA-7297

SSA-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-69167184

done
Create USNO download acknowledgementUSNO Proprietary Download System/A way to deliver data from projects that are not archiveddone





VLA Metadata Presentation 

Anchor
VLAMetadata
VLAMetadata

VLBA Polarization Duplication-387e-8345-36eee8a98f01String Terminators in VLBA fieldsBL473 unlock and missing segments71487184Remove Legacy Archive label and link from new archive7375
Priority/Done?NotesJiRA ticket /Confluence page
critical

Scan list does not show coordinates between dec= 00 and dec = -1 correctly

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

7620


Critical (4.3.0)Make scanlist information useful 

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

keySSA-5640
done

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

This ticket has multiple points to make the new tool match the Legacy archive and to have the displayed data be much more useful.
High (4.3/4.4)VLA Metadata display updates. 

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-5641done

WS-1390

This has many items including 'telescope observing logs'.
Medium

Incorrect metadata sometimes displayed for projects with duplicate proposal IDs between VLA and VLBA

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-

7318


doneMediumVLBA data structure in the new archiveVLA/VLBA proposal code degeneracy
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
5538

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-71827318


MediumIndexing 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-71837187


Subscans table holding both Radian and Degree positions

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
USNO Proprietary Download System/A way to deliver data from projects that are not archiveddone

5275

done
archive search returning incorrect 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-
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.
6192


done





Legacy VLA Data

Anchor
Legacy
Legacy
VLA Metadata Presentation

Incorrect metadata sometimes displayed for projects with duplicate proposal IDs between VLA and VLBA-7318
Priority/Done?NotesJiRA ticket /Confluence pageMake scanlist information useful 
Criticalcorrupt legacy VLA data in the AAT

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-7188
 https://open-confluence.nrao.edu/display/SRDP/VLA+Metadata+Display+Updates

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

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


HighMetadata Issues in Legacy VLA 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

-7192

Needs input from Bryan
HighLegacy VLA data missing error codes in the new archive toolVLA/VLBA proposal code degeneracy

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

7191

Mapping of quality errors were lost. Stephan will continue following up with Bryan. Blocker for LA retirement.
Highmetadata errors in VLBA (BD114) and old VLA data in 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-
7318
Indexing of VLA low band projects
7128

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-7187
keySSA-7129

This has been split into two tickets: one VLBA and one VLA
Mediumlegacy VLA metadata error: EBs that claim to have run for 2+ daysDatabase 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-7277

7129

requires re-ingestion


Data Integrity

Anchor
Integrity
Integrity

Subscans table holding both Radian and Degree positions5275
Priority/Done?NotesJiRA ticket /Confluence page
BlockerGap Analysis Between Legacy and 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-
6222


can be done once RLSW finishes the AIPSFITS files
CriticalAutomated annotations for missing scans/BDF, Automated Error Recognition of Ingested Datadonearchive search returning incorrect 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-

6192
done

Legacy VLA Data

Legacy VLA data missing error codes in the new archive tool7191legacy VLA metadata error: EBs that claim to have run for 2+ days-7129

CriticalDisplay of archive ingestion/observation issuesPriority/Done?NotesJiRA ticket /Confluence pageMetadata Issues in Legacy VLA 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-7189


related to SSA-7192Needs input from Bryan7190
CriticalIdentification of ingestion problems and automatically fixMapping of quality errors were lost. Stephan will continue following up with Bryan. Blocker for LA retirement.metadata errors in VLBA (BD114) and old VLA data in new archive

Example ticket of a silent failure: 

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-

7566

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-7665


create missing db entries for Flag.xml7128
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
-7129
This has been split into two tickets: one VLBA and one VLA
-6273


Done
fix ASDM.xml files missing FlagTable entities
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
requires re-ingestion

Data Integrity

-6274


Done


DA Tools for Data Editing

Anchor
DATools
DATools

Automated annotations for missing scans/BDF, Automated Error Recognition of Ingested Data
Priority/Done?NotesJiRA ticket /Confluence page
Tool for setting Proprietary Period of science observations on the VLA and the VLBAhttps://open-confluence.nrao.edu/pages/viewpage.action?spaceKey=SPR&title=Tool+for+setting+Proprietary+Period+of+science+observations+on+the+VLA+and+the+VLBA
CriticalDA annotation tools/Archive data annotation toolsPriority/Done?NotesJiRA ticket /Confluence pageGap Analysis Between Legacy and 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
key

SSA-6222can be done once RL finishes the AIPSFITS files

WS-1392
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-7190

WS-1393
WS



Missing Data

Anchor
Missing
Missing

open-confluencedisplay/SRDP/Archive+Data+Annotation+Tools7189create missing db entries for Flag.xml6273fix ASDM.xml files missing FlagTable entities6274
Priority/Done?NotesJiRA ticket /Confluence page
Critical
  • VLA/VLBA Image archive contents should be migrated into AAT (https://
Display of archive ingestion/observation issues

Tix to be 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

,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keyWS-1394

May require discussion about how new archive will display images and the uvfits datasets.


HighALMA Standard images into AAT

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

related to SSA-7190

7278


HighLarge project support - ALFALFA + Other collection ingest

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

7437
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


Other

Anchor
Other
Other
DA Tools for Data Editing

Tool for setting Proprietary Period of science observations on the VLA and the VLBAconfluencepagesviewpage.actionspaceKey=SPR&title=Tool+for+setting+Proprietary+Period+of+science+observations+on+the+VLA+and+the+VLBA
Priority/Done?NotesJiRA ticket /Confluence pageDetails

Other tickets (so they are not forgotten)

https://open-

DA annotation tools/Archive data annotation toolshttps://open-confluence.nrao.edu/display/SRDP/Archive+Data+Annotation+Tools

Missing Data

Tickets remaining are listed throughout their respective categories.
Critical

Proposal Contact Author not added to data.nrao.edu database

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

Bug when a project uses different PI and Contact Author
MediumPreserve login between AAT and my.nrao.eduPriority/Done?NotesJiRA ticket /Confluence pageALMA Standard images into AAT

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

Large project support - ALFALFA + Other collection ingest

Other

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-7322


√ (4.2.0)Remove pop-up page when accessing data.nrao.edu

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

Priority/Done?NotesJiRA ticket /Confluence pageDetails
Other tickets (so they are not forgotten)

Proposal Contact Author not added to data.nrao.edu database

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

Bug when a project uses different PI and Contact Author

7502



ALMA

Anchor
ALMA
ALMA

Priority/Done?NotesJiRA ticket /Confluence pageDetails
CriticalALMA MOUS/calibration ingest unreliable; ALMA butler implementation into productionPreserve login between AAT and my.nrao.edu

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-7482



Product Versioning

Anchor
Versioning
Versioning

Priority/Done?NotesJiRA ticket /Confluence pageDetails
CriticalNeed to allow multiple versions of products (images/calibrations) in the archive

Product Versioning and Replacement Design

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