uchic / h2outility Goto Github PK

The current design requires "Apply" to be clicked before the script is run. This is not obvious to the user. We either need to put the "Apply" button lower on the page (i.e., next to "Stop Script" and "Run Script") and maybe include an instruction there, OR we need to remove the requirement for clicking "Apply".

Generate CSV files with the time series values.

• CSV files should be divided for each Site, QC Level, and Source.
• Users should be able to choose whether to group multiple series into a single file, or to generate a single file per time series.
• File headers should provide information about the series they contain

When "Clear Changes" is clicked, the title and abstract remain. The funding information is cleared.

Implement and test a user interface that allows the user to easily understand and use the H2O utility, similar to the example below.

I specify how files should be organized using the visual updater. When updates are made form the GUI, it performs as expected.

These specifications get written to the operations file ("single file" and "chunk years").

When I close and reopen the visual updater or run the headless/silent updater, the file organization specifications are reset. Both are unchecked. They are also reset in the operations file. They need to persist.

Implement a script that performs the user-specified actions without using the GUI interface.

In the operations file, the block that specifies the series to be added to the file is only present on the 2 most recently added resources. For the other, previously specified resources, it is completely missing. This may have something to do with the functionality of the tool to add resources to HydroShare.

For the files with a single series, the qualifier codes are included as a column. However, there is no header block with qualifier codes and definitions. This was present in previous versions of these files.

When the interface creates a resource, it is private by default. We need some sort of functionality/toggle to make a resource public.

HydroShare resources need keywords. We need the interface to have the functionality to add keywords

I have tried to run the headless script as a windows task without success. Here is my set up (which may be incorrect), and here are the errors I get.

Make it easier for the user to find and select the ODM series they want to use. Options include allowing users to change sorting of the ODM series, and to select/deselect multiple series based on site, QC code, variable, source, etc.

Users should be able to:

• View all resources they own
• Create new resources
• Edit resource metadata (title, abstract, award information)
• Select the time series to be uploaded to a specific resource
• Upload the generated CSV files to the selected resource

We need to figure out a way to help users understand the ID and Secret fields and to let them know how to populate these.

Right now, the tool sets the author and owner to the HydroShare user that has the API key. This is OK for the first version, but users will want more control over authorship as the resources are created the first time.

The GUI is used to create a resource and specify the series and files to be included. The resulting operations file includes a line for the paths of the files to be loaded. This line is populated with file paths for the first resource created, but for subsequent resources is blank.

I thought this might be related to the headless script only updating the files for the first resource (Issue #30 ), but when I manually added file paths, there were still issues. The specified files were loaded to HydroShare; however no new files were written locally that weren't before present.

Note the "Associated Files" fields:

When a user chooses to upload two or more sites to a single HydroShare resource, use two bounding points to create a spatial box coverage.

CSV files will need headers that describe the datavalues they contain. CSV files are chunked by site, QC level, source, and (optionally) year. The CSV headers should contain the following:
Expanded site information (line 710 in CSVDataFileGenerator)
Expanded source information (line 738 in CSVDataFileGenerator)
QC Level disclaimer (lines 665, 700 in CSVDataFileGenerator)
Variable information for each column (line 822 is compact variable information, line 774 is expanded variable information)

Headers can be created and written to files around lines 256 and 296 in H2OServices.py

If you pick an existing resource in HydroShare and then set the title, or abstract, or funding agency information in the tool, which wins? HydroShare or the tool? Right now, when the tool runs, it will set the metadata in HydroShare to what is in the tool, but there may be some instances where the following happens:

1. The tool creates the resource
2. The user edits the metadata of the resource in HydroShare
3. The user runs the tool again, but doesn't want the tool to overwrite changes they have have made to the metadata in HydroShare.

So, need an option that specifies whether the metadata should be overwritten or not if it already exists.

The headless script works as expected when there is a single resource specified in the GUI and the operations file. However, when additional resources are added/specified, the headless script only works for the first resource.

Here is a screen shot of the log file. Notice that files are only created for a single resource.

To prevent file naming conflicts, when chunking CSV files by series we should add the method to the filename.

Need to ensure that the series specified for each resource in the config/operations file are shown in the GUI for each resource.

If a user has Quality Controlled series without the "One series per file" box checked, the Qualifier and Censor information for those values is not preserved. Show a modal window that informs users of this when they add QC series without that box checked.

Generated files should use the format {site_code}_{variable_code}_{quality_control_level_code}_{source_id}.csv

When connecting to HydroShare or to the database, the popup that indicates success/failure of the connection flashes 2x - sometimes more.

Right now we are writing data to CSV files because that's what the iUTAH people wanted. But, HydroShare has a specific resource and file type for time series. We should add an option for writing to that type rather than to CSV. Next version.

To make resource management easier for the users, we should add a button to the GUI that allows users to delete all files from the selected resource. To be safe, we should also have the user confirm the deletion so they don't accidentally remove all their files.

Add button to the GUI to update the config/operations file. There should be two separate buttons- one to save the configuration and one to upload series/run configuration file.