Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362005-10-04T17:07:37ZEcoinformatics Redmine
Redmine Bug #2220 (Resolved): Temporal coverage on Data Registry formhttps://projects.ecoinformatics.org/ecoinfo/issues/22202005-10-04T17:07:37ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>In the Temporal Coverage of Data section of the NCEAS Data Repository form<br />(<a class="external" href="http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas">http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas</a>), the<br />year, month, and day are indicated as being required. However, if you enter a<br />year, but don't select a month and/or day (leave them as "0"), you don't get an<br />error message for the missing month and day, and the values that you left as "0" <br />become "1" (01 01 yyyy).</p>
<p>We should allow the user to provide the year only (month and day would not be<br />required fields), and the month and day should not be displayed if they were not<br />selected.</p> Bug #2218 (Resolved): Data medium info not saved in editing modehttps://projects.ecoinformatics.org/ecoinfo/issues/22182005-09-30T20:26:27ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>When you go back to the data registry form (this was for the NCEAS skin) after<br />getting a failure message (by using the link in "Click here to return to the<br />form, fill in the required fields, and submit the data set description again"),<br />the option that was previously selected under "Data medium" doesn't appear,<br />i.e., the info previously submitted wasn't saved.</p> Bug #2217 (Resolved): Change output text for Usage rightshttps://projects.ecoinformatics.org/ecoinfo/issues/22172005-09-30T20:08:09ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>Under the "Usage Rights" field, when you select "Obtain permission from data set<br />owner(s)" the output (what appears in the data package) is simply "permissions".<br />The output should be "Obtain permission from data set owner(s)".</p> Bug #2215 (Resolved): NCEAS skin: NCEAS Project(s) should be a required fieldhttps://projects.ecoinformatics.org/ecoinfo/issues/22152005-09-30T19:45:04ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>On the NCEAS data repository form<br />(<a class="external" href="http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas">http://knb.ecoinformatics.org/cgi-bin/register-dataset.cgi?cfg=nceas</a>), the<br />field "NCEAS Project(s)" should be a required field. If you don't select<br />anything from the drop-down menu and click on the submit button, you don't get<br />an error message saying you should have selected a project.</p> Bug #2214 (Resolved): Submitting lat/long coordinates in spatial coverage sectionhttps://projects.ecoinformatics.org/ecoinfo/issues/22142005-09-30T19:40:01ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>A data package was created using the NCEAS Data Repository form. When<br />coordinates 53 deg, 34 min, 0 sec N, and 0 deg , 2 min, 0 sec W were entered in<br />the SPATIAL COVERAGE OF DATA section, this error message came up:</p>
<p>Failure<br />An error occurred. Please check the list of errors below:</p>
<ul>
<li>cvc-complex-type.2.4.b: The content of element 'geographicCoverage' is not<br />complete. One of '{"":boundingCoordinates}' is expected.</li>
</ul>
<p>Click here to return to the form, fill in the required fields, and submit the<br />data set description again.</p>
<p>It didn't seem to like the 0 degrees for the longitude because when it was<br />changed to "1", it worked.</p> Bug #1980 (Works For Me): Duplication when displaying catalog of data packageshttps://projects.ecoinformatics.org/ecoinfo/issues/19802005-02-14T22:19:19ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>If you query data package nceas.177.4 on the KNB web site or the NCEAS Data<br />Repository, you will notice that the information in the Contacts and Keywords<br />columns is duplicated (in the original document, each keyword is provided only<br />once). This also happened for some dps that I created (have since been deleted<br />from network).</p> Bug #1948 (Resolved): Changes in Data Registry (NRS, LTSS, OBFS) Format for ESAhttps://projects.ecoinformatics.org/ecoinfo/issues/19482005-02-09T22:39:35ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>This is a request from Mark Stromberg (<a class="email" href="mailto:stromberg@berkeley.edu">stromberg@berkeley.edu</a>):</p>
<p>Here is a list of things to change for making it more general and include best<br />practices. This both includes a report on a lot of the discussion and a guide<br />for someone actually changing the HTML code in the Guide and on the web form. <br />This is aimed at the web form for ESA. So, the changes should be first<br />implemented in the current LTSS page. Then we can migrate to NRS pages, etc.? I<br />think if you did the LTSS page, NRS and OBFS could do their own editing (Me,<br />Marsh, Kevin Brown)</p>
<p>Overview and Introduction<br />We should put something like this in both the Guide and webform:</p>
<p>What is the Registry?<br />A way to discover data, or more clearly, the person with a data set. Any links<br />provided to real data sets are only potential links, as there is no data archive<br />(yet). So, much of the data registry is focused on letting a user track down<br />individuals who either authored some ecological data, or know where to find it.<br />When an ecological data archive with contributed data sets exists, the registry<br />can provide links to the actual data. For now, the registry is a means to find data.</p>
<p>Revise the format to reflect usability. Consult with Laura Downey.<br />Shade each section<br />Include boxes with examples: Good Examples .vs. Bad Examples<br />Have suggestions under "Bad Examples" and suggestions on "Good Examples" <br />Then, by each section: match the field names in the web form to the field names<br />in the Guide. Need a complete check of Guide to exactly match the web form.</p>
<p>Basic Information<br />Station Name (in Guide): change to Organization Name (webform): For ESA, no pull<br />down, but Organization. Need examples:</p>
<p>User friendly format change<br />Good: National Center for Ecological Analysis and Synthesis<br /> University of Michigan Biological Station<br /> Duke University FACE Facility</p>
<p>Bad: University of California Santa Barbara<br /> Michigan Station<br /> Duke University</p>
<p>Data Set Title<br />User friendly format change<br />Your examples, good and bad are fine; split in boxes. Continue to use the<br />related pairs; a good example and a bad example from each.</p>
<p>Data Set Originator (Guide) .vs. Principal Data Set Owner<br />User friendly format change.<br />"Originator Role" only on Guide. ..not in web form. We should explain in the<br />Guide, and maybe on the web form that the "Originator" is traditionally what<br />ecologists consider to be the "author". Additional Originators are comparable to<br />"co-authors" <br />Check for typos; "not required of you provide" in Guide.</p>
<p>Additional Originators (in Guide) yet "Associated Parties" on web form<br />User friendly format change<br />Maybe show two lines so you immediately know more than one can be there.<br />Add some description of what each role. I like the reduced number of roles, but<br />could add a user-defined role? Or add 1 or 2 more of the roles in the full<br />Morpho set?<br />Here, we might allow people to have more than one role assigned to each<br />additional originator. Also allow a field that can be filled in with "Different<br />From Above".<br />"Originator" is confusing..is it the same as PI?<br />"Metadata provider" is confusing; this is the person filling out the form?<br />Add "Data Poacher"....(Reichman).</p>
<p>I think the consensus was that we need a section called Attribution that lists<br />those who receive credit for the data's existence. We might want to use names we<br />already know like Authors, Co-authors? We need to talk more about this. Or,<br />maybe the clarification in the first field might eliminate a need for "Attribution".</p>
<p>Data Set Abstract<br />User friendly format change<br />Good Example (ok in guide) but need a bad example.</p>
<p>Keyword Information<br />User friendly format change<br />Looks good; matches</p>
<p>Temporal Coverage of Data<br />User friendly format change<br />Looks good, matches</p>
<p>Spatial Coverage of Data<br />Remove the "Use Station Coordinates" <br />Maybe install a place name look up for coordinates...see COREO site that uses<br />the place name (address, street name, etc.) that generates the Latitude and<br />Longitude. If so, put the address before this...<br />Rest looks ok..</p>
<p>Taxonomic Coverage of Data<br />User friendly format change.<br />Three fields, each needs instruction (Taxon Rank, Taxon Name, Taxonomic Authority)<br />Here, we need to add some language that is explanatory. We suggest:<br />There are two fields that will allow people to find the level of taxonomic<br />resolution associated with the data being described. You could include a list of<br />species, with "species" in Taxon Rank, and the name "Ursos arctos" in the Taxon<br />Name. Or, if the data set does not include information based on specimens<br />identified down to the species level, then "Genera" and "Ursos" If the data only<br />include determinations to a higher taxonomic concept, say "Tribes" and<br />"Oryzeae". etc.</p>
<p>Taxonomic Authority: Consensus was that we want the resource one used to<br />identify the taxon or associate a taxonomic concept. For instance, the reference<br />citation for the field guide, key, or nomenclature revision.<br />Suggest that people check in with Glasgow Name Serve or ITIS<br />(<a class="external" href="http://www.itis.usda.gove">www.itis.usda.gove</a>) before they enter their taxa names to avoid mis-spelling.<br />Provide links near data entry field, or put link in guide.</p>
<p>Methods<br />User friendly format change.<br />"Add Paragraph"- what does this do?; why not just keep writing in the box?</p>
<p>Data Set Contact<br />User friendly format change.<br />Again, is there some way we can ask people for a geographic name of where the<br />data were taken and let it generate the Lat and Long? If so, maybe this could be<br />moved up? But, then, we are asking different questions. This is about<br />discovering where to find a person. So, it is fine as it is.</p>
<p>Distribution Information<br />User friendly format change.<br />Dataset Name or Identifier: Give some examples of data identifiers, good and<br />bad. Reference to "filename and path" in Guide is jargon and they are so<br />ephemeral anyway, don't mention them. Delete reference to "station"; replace<br />with organization. Give some good and bad examples of dataset names, maybe from<br />LTER dataset names.</p>
<p>Data medium; give examples; paper, digital files, video tapes, etc.<br />Clearly point out that if any URL provided should be as permanent as possible<br />and that no guarantee that the data may be there in the future, as local<br />computers and servers change names rapidly.</p>
<p>Additional Information/Remarks (Guide) and Additional Information (web form);<br />suggest user describe the data format; Excel, Access, FoxPro, DBase, or any of a<br />large universe of data formats.</p>
<p>Submit Dataset<br />User friendly format change.<br />Very confusing. The web form says....<br />NOTE: You must submit your data in order for these to be entered in the Data<br />Registry! This phrase suggests that the actual data must be submitted somewhere.<br />Just delete the phrase?<br />Make the "Submit" button clearer. The button should say "Submit Metadata<br />Described Above", or something to that effect. The Reset button is dangerous.</p> Bug #1819 (Resolved): Access control - deny public/allow user read: user couldn't readhttps://projects.ecoinformatics.org/ecoinfo/issues/18192004-12-08T20:01:44ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>I created three DPs for which I had set the Access Permissions so the public<br />would be denied access and I (uid=connolly,o=NCEAS,dc=ecoinformatics,dc=org)<br />would be allowed to read. When I tried accessing the data from the KNB web site<br />(after I logged in as uid=connolly,o=NCEAS,dc=ecoinformatics,dc=org), I got a<br />message saying "User public does not have permission to read the document".</p>