| Priority/Done? | Notes |
|
|
| high | Scriptable query interface | Scriptable Query Interface to NRAO Archive | Jira |
|---|
| server | DMS JIRA |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-7395 |
|---|
|
|
|
| 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 |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-4915 |
|---|
|
| Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-7497 |
|---|
|
|
|
| high | Position searches provide distance from searched position and sort by distance | | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-7387 |
|---|
|
| User request, but is a legacy AAT feature |
| medium | Treat wild cards consistently in AAT search interface - account for * in source names
| | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-7496 |
|---|
|
|
|
| low | Allow search return of observation scans? | | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-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 |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-7424 |
|---|
|
| Based on legacy archive helpdisk question from user. UC feedback as well. |
| medium | Fix 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 |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | SSA-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. |
