Versions Compared

Old Version 78

changes.mady.by.user John Tobin

Saved on

compared with

New Version 79

changes.mady.by.user John Tobin

Saved on

Key

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

...

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.

...