Priority/Done? | Notes |
|
|
| Scriptable query interface | Scriptable Query Interface to NRAO Archive Jira |
---|
server | DMS JIRA |
---|
serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
---|
key | SSA-7395 |
---|
|
|
|
| Fix Frequency-dependent FOV and position searches | 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 |
---|
|
|
|
| Position searches provide distance from searched position | 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 |
| Treat wild cards consistently in AAT search interface | 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 |
---|
|
|
|
| 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. |
| Allow search filtering based on integration time. | 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. |
√ | 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. |