uchic / ckandev Goto Github PK

I think there should be some text under the "Keywords" entry box telling users that commas should be used to separate a list of keywords.

The iUTAH study area drop down list on the "Create dataset" page needs to be modified to list the following items:

Logan River Watershed
Red Butte Creek Watershed
Provo River Watershed
Wasatch Range Metropolitan Area
Other

The preview functionality for pdf resources is not fully functional. See the screen shot:

On UI we are showing keywords required (field is marked with *). However, the current code does not enforce this requirement. Not sure if they are required or not. In CKAN it is optional by default.

Do we want all of these additional details available for viewing for each resource? It seems to me that these are mostly internal pieces of data that aren't very useful for viewing.

We have example entries implemented somewhat, but there is not yet any mouseover help. Also, is there a way that I could edit the example text and the mouseover help?

If I have created a dataset and then deleted it, I am unable to create a dataset using the name of the deleted dataset because the url is already in use. See the screen shot:

See http://dublincore.org/documents/2000/07/11/dcmi-type-vocabulary/ for the list of DCMI Types that should appear in the "Type" drop down list on the "Create dataset" page.

We need to think about adding shapefiles. As you know, there are multiple files with various file extensions that comprise each shapefile. It is pretty tedious to have to add each of these files individually. Multiple file upload to a single data resource is not functional. Another option might be to encourage users to zip files together. Not sure if that would be the preferred method?

Some of the required and optional metadata elements are repeatable. Examples include - creator, contributor, etc. These need to be implemented per the iUTAH metadata schema specification.

We determined not to implement relation and versioning yet. Should we remove this field from the metadata entry? If not, we need to clarify and narrow the intent. For example, we could specify that "Relation" should be the url of another dataset submitted to the iUTAH system. However, I don't think that it's very useful as we don't have repeatable metadata elements implemented yet.

For the dataset that I had previously loaded, I went back and tried to edit the creator and maintainer information. When I clicked "Update Dataset" I get a "404 not found" error.

When I checked the dataset, it had been switched from public back to private (I didn't want this). Also, it looks like the Creator name and Maintainer name were set correctly, but the address, phone, email, etc. for the Creator did not get set.

The "Update Frequency" drop down on the Dataset creation page needs to be updated to include the following items:

Hourly
Daily
Weekly
Yearly
Other
None

Due to the facet count update that we are doing in our extension now, some of the facets end up with zero counts (e.g. a tag is shown as 'water (0)'). I think we need to remove such facets from display.

If we are controlling and assigning visibility, should the "Visibility" field even appear on the metadata submission form?

I uploaded a relatively small CSV file with some time series data in it. I click to preview the file and I get a spinning icon for a second and then I get an error message that says:

This resource can not be previewed at the moment. Click here for more information.

Could not load preview: DataProxy returned an error (Data transformation failed. HTTPException: Deadline exceeded while waiting for HTTP response from URL: http://iutah-ckan-test.uwrl.usu.edu/storage/f/2014-02-20T00%3A32%3A21.845Z/lbr-mendon-dissolvedoxygen-qc1.csv)

I created a new dataset and specified the organization, address, and phone number for the Creator. When I view the metadata for the resource, none of these are listed. The Creator and Maintainer names are set - but I don't know if they are set to my name as the submitter by default or if it accepted what I input to the form because I didn't change them.

It would be helpful to be able to cancel a file upload. This is particularly true for large files for which ckan appears to stall on. This brings up a larger issue, which is that there appears to be some sort of file size limit (1 GB?), but it isn't listed anywhere, and we may need to load larger files.

When I view the metadata for a dataset, the "Additional" metadata tab wraps to a second line. It would be better to shrink the tabs a little bit so they all fit on one line. I suspect this is just a CSS issue.

Which data licensing are we assigning/following? In most places on the site, it says "Creative Commons", but when metadata is entered, it refers to the Open Database License.

I just made a dataset public. It shows up under my personal profile and it shows up as a dataset under the organization. But, if I just click on the "Datasets" link it doesn't show up. The page says "1 dataset found" but nothing is in the list.

Are we going to support the entry of a metadata only record?

When using “Save and add another”, the user is not shown which files/resources have already been added to the dataset. It would be helpful to see what has already been added to avoid duplication.

For example, when editing the dataset, a user can see the resources that have been added in the left panel:

Now whenever we make changes to our dataset schema, any already existing datasets will fail dataset view or editing. Since dataset schema change is not avoidable, we have to find a way to make the old datasets to cope with new schema.

The last step in submitting a dataset to the iUTAH CKAN instance should be agreeing to a data publisher's agreement. I have the text of the agreement written, but it would be implemented as a step they must click through before their dataset get's created in the system.

It seems the "Update Frequency" field fails when one selects some of the provided options. The existing code uses a regex pattern as a validation for this field. I think we need to remove that validation since we are giving certain known value options for the user to select. No validation needed I think.

The screenshot shows that there is only one public dataset, but the numbers in the facet selection pane indicate that there are a total of three datasets. The two invisible datasets are those that are still private, so their attributes shouldn't appear in the facets pane.

When I am on the page of a dataset and I click on one of the tags, I get an error telling me that there are no datasets. There are actually several datasets that have that tag. When clicked from elsewhere, the tag link works as expected. See the below screen shots.

Should we have any of the Creator and Maintainer information be required?

The data processing method metadata field will currently only allow 100 characters. It should be reset to allow up to 500 characters.

When adding data resources, the "Name" should be required. It is automatically completed when the resource is an uploaded file, but for a links to a file or a link to an API, the user should need to enter a name.

To accomodate dataset for which there is no updating going on.

The data collection method field in the metadata template will currently only allow 100 characters. It should be reset to 500 characters.

It appears that when I have entered metadata without adding a data resource, the dataset appears as a "Draft" under "My Datasets". How do I delete these entries? If I add a data resource, it is no longer a draft.

When a file/resource is deleted from a dataset, it still appears as one of the clickable file types under the dataset on the "Dataset" pane. The "Format Type" of a deleted resource also still appears in the facets pane after it has been deleted. It is only after the entire dataset is deleted that those artifacts are removed.

If we are controlling and assigning visibility, should the "Visibility" field even appear on the metadata submission form?

When I upload a file and add the file level metadata and then click the button to go to the next page I get a server error.

The full list can be found here: http://dublincore.org/documents/resource-typelist/

Is "Creator" required for a "Citation" to be generated? If so, we should add text to the "Additional Data" page stating that Creator information must be completed for a Citation to be generated.

We did not include "Intended Use" in our metadata elements schema. I suggest we remove it from the metadata entry as it is covered by "Purpose".

Are all of the datasets going to have an organization of iUTAH? If so, then should this field be automatically assigned? Or, do we want people to have the opportunity to create and/or change the organization?

The user may edit the "Format" of a file, but it is not clear what format is automatically assigned on the "Add Data" page (so the user does not know whether or not to edit). The automatically assigned format doesn't show up until viewed on the "Datasets" page. In the example below, "png" should show up in the format field.

Users downloading data should agree to the iUTAH data use agreement. When they click to download a dataset/file, they should be presented with the data use agreement text and have to agree or not. I have the text of the agreement written, it just needs to be implemented.

The default entries from fields with selection appear in the metadata tabs even when those entries are optional and the user may not have changed them at all. (In the below example, the update frequency was not edited, but it defaulted to "Daily".) They should either not be assigned or else the fields should default to a null.

This is just a styling issue. It should be on the same line as the label.

I started creating a dataset. Then, I accidentally clicked away to another link. Then, I clicked on my name at the top of the window to see my datasets. The dataset I was created is there in my list as a draft. But, when I click on it, I get a Server Error.

After describing and loading a dataset, it does not appear in the "Datasets" section because it is "Private". We should include a note on the final submission screen informing users that they can still access their entry under "My Datasets", but that it won't be generally accessible until moderation occurs.

How are we envisioning that groups will be implemented? Perhaps we need some groups established in the system to provide some examples.

I just created a new dataset and uploaded a single file. When I view the metadata for the new dataset, there is a second file there that I didn't add to the dataset when I uploaded it. It is the data file for the last dataset that I created.

I received an error for not adding a data resource. When I then added a resource, the error was still on the screen: