Versions Compared

Key

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

...

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
    Priority/Done?NotesJiRA ticket /Confluence page
    CriticalDownloads via Scriptable query interface

    Scriptable Query Interface to NRAO Archive  

    SSA7474

    Don't restrict download number limit.

    New ticket to remove the '/100 string from webpage'Bulk download of Calibration tarballs7353Data Delivery times out if tar file(s) are too large/time consuming6083archive-new delivery not chmod'd/chownedmake tar downloads default to 'off'7344
    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
    key

    WS-1395


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

    confusing to staff as well

    -need to kill RH, WS 3.0+

    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-

    7106
    could be a flyover text (currently has a flyover circle with slash)

    7474

    confusing to staff as well

    -need to kill RH, WS 3.0+

    criticalRestore data using same version of CASA as calibratedhigh (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.

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

    WS 2.7 or 3.0?attempted for 4.2.0 but is deferred

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

    Delivery Directory Improvements

    7352
    Jira
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype
    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-74367000

    WS 2.7 or 3.0?
    planned 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/deselect2

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

    mediumDownload weblogs directly (and/or serve them as well!)Direct weblog download from archive search return interfacemedium

    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-

    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.

    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
    low

    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-

    will not be an issue with taring not being the default.low

    7573


    mediumDownload weblogs directly (and/or serve them as well!)√ 2022.2 pipelineoption to return UNTAR'd file does not work 

    Direct weblog download from archive search return interface 

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

    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
    keySSA-6495
    https://open-confluence.nrao.edu/display/SRDP/Product+lists+for+Basic+and+Calibrated+Measurement+Set+downloads

    pipeline topic

    WS-1389
    !


    mediumBulk download of Calibration tarballs

    Jira
    server

    √ (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-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
    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-
    7345
    6083
    will not be an issue with taring not being the default.
    lowarchive-new delivery not chmod'd/chownedThis 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-
    7343
    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-

    ...

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

    ...

    Priority/Done?Noteshigh

    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

    7179

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

    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!
    disable checksums by default

    Jira
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype,created,updated,duedate,

    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-

    7497high (4.2.2)

    Position searches provide distance from searched position and sort by distance

    7343


    make tar downloads default to 'off'
    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-7344



    Search interface/Data Selection

    Anchor
    Search
    Search

    7387issuekey,summary7496Scriptable Query Interface to NRAO Archive eb2e750b-a83a-387e7395
    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

    User request, but is a legacy AAT featuremedium

    Treat wild cards consistently in AAT search interface

    • account for * in source names
    Jira
    serverDMS JIRA
    columnIds

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

    lowAllow search return of observation scans?

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


    high (4.2.2)

    Position searches provide distance from searched position and sort by distance

    • legacy archive feature

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

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

    7387

    User request, but is a legacy AAT feature
    medium

    Treat wild cards consistently in AAT search interface

    • account for * in source names
    mediumFix mosaic position searches for VLASS and ALMA mosaics (subscan vs. scan)Rearrange boxes in 'Search Inputs'Ticket to be created.√ (4.2.0)Scriptable query interface

    Jira
    serverDMS JIRA

    serverId

    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?

    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.

    ...

    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)

    ...

    Priority/Done?NotesJiRA ticket /Confluence pageHigh

    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
    key
    SSA
    WS-
    7350

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

    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

    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

    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
    serverIdeb2e750b-
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySSA-
    7436
    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 PIHigh (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-75637423


    High (4.2.1)Proxy issue for huge VLBA projects

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


    High (4.2.1)Slow VLBA indexingMedWrong band designation in VLBA data (old data only?)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

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

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

    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-

    7185 but needs to be picked up in future AAT releases

    7541


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

    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.

    Med

    7420

    This is in both the legacy archive and the new archive tool. Issue needs more research on how prevalent it is; unclear.MedDefault Instrument of VLBA projects in AAT/PPI
    • 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-
    7208And a new ticket created:
    • 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-7619
    Confluence req: VLBA:
    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/PPIMedAdd 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

    Low

    7208

    And a new ticket created:

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

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


    MedAdd PFT (proposal finder tool) link in Project View for VLBA projectsLowMark4 files with 0 length getting added to new archive metadata

    Jira

    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.

    7461


    LowImport remaining 8 GMVA filesLowIncomplete 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-69167438


    LowMark4 files with 0 length getting added to new archive metadataHighCreate 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?

    7297

    Small number of files affected.LowIncomplete VLBA data of observations crossing midnight (open in case more cases show up)Remove Legacy Archive label and link from 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-73756916


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

    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.


    (reopened) Low?
    Remove Legacy Archive label and link from new archive√ 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

    7375

    Jira
    serverDMS JIRA
    columnIds
    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-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.12.10Add 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 GP0024Add 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-
    7328
    7426


    √ 4.1.1old VLBA project metadata issues

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


    √ 4.1.1VLBA data structure in the new archive - improved interfaceold 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-7379


    √ 4.1.1VLBA data structure in the new archive - improved interface

    Jira
    serverDMS JIRA
    serverIdserverIdeb2e750b-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

    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 entries

    Jira
    serverDMS JIRA
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySSA-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 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-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-5640

    done√String 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

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

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



    ...

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

    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. 

    https://open-confluence.nrao.edu/display/SRDP/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
    keyWS-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


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

    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


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


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


    done




    ...

    6273
    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 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-7190
    https://open-confluence.nrao.edu/display/SRDP/Archive+Data+Annotation+Tools


    CriticalDisplay of archive ingestion/observation 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-7189


    related to SSA-7190
    CriticalIdentification of ingestion problems and automaticallyfixautomatically fix

    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

    create missing db entries for Flag.xml

    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.xml
    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-6273


    Done
    fix Donefix 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-6274


    Done

    ...

    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 tools/SRDP/Archive+Data+Annotation+Tools

    /SRDP/Archive+Data+Annotation+Tools 

    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-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
    keyWS-1393
    WS



    Missing Data

    Anchor
    Missing
    Missing

    Priority/Done?NotesJiRA ticket /Confluence page
    Critical

    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
    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-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-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-5712
    ALFALFA: SRAO and Collection Support


    ...