Custom Query (61 matches)
Results (49 - 51 of 61)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #37 | fixed | Write logs of users' interactions with archive | ||
| Description |
We would like to know what is happening with the archive, so we should have the archive write to a log file when users make a query and download data. The log entry should have things like date, time, username/email, query string, download size, whether they viewed profiles, ... Dick's suggestion -- just write all out in one long text line, with defined columns that could be searched by awk (for instance). |
|||
| #38 | fixed | Select based on project ID | ||
| Description |
It might be good to be able to select only observations for a given project ID. |
|||
| #40 | fixed | archive search - implement proprietary period limits | ||
| Description |
Data taken recently (within the "proprietary period") must not be made available to users outside the observing team for those observations. The search code needs to implement:
|
|||
Note: See TracQuery
for help on using queries.
