NOAA change requests list

[chrismheiser]

Per the e-mail that Wendy sent. Here are the list of requests to add/change on the playground.

Request 1. Support a new “NOAADataType” (or Chris/Nick suggest a LiPD tag name) field, in addition to continued support for the LEO/LiPD Archive Type field.

Reasoning: there is no completely unambiguous and programmatically cross-walk possible between the NOAA Data Type and LiPD/LEO Archive Type, because in some respects they are logically different. LiPD specifies an Archive Type for the overall dataset (required) and each measurement table column (optional), whereas WDS-Paleo defines one data type for the overall dataset, and one or more for each measurement table column (both of which are required). Both the LiPD Archive Type and WDS-Paleo NOAA data types are valuable information and support for both together provide richness of meaning.

Specific requests:

Add a "NOAADataType" field to the Playground in this “NOAA” section, as well as to every Playground LiPD MeasurementTable column (as will be detailed below in Requests 8. And 9.).

When outputting the NOAA WDS-Paleo Template:

1. Change the NOAA WDS-Paleo Template “Archive” field name to “Data_Type” (this is located in the NOAA WDS-Paleo Template general metadata section, towards the top of the template).
2. Populate the NOAA WDS-Paleo Template ”Data_Type”tag with the value of the Playground NOAADataType field.

Request 2. Add Playground field “NOAA Study Name” and corresponding LiPD NOAAStudyName tag, and populate LiPD and NOAA WDS-Paleo Template metadata with its value

a. Add field “NOAA Study Name” in the NOAA Section of the Playground

b. When the user selects “create LiPD”’ and/or "download NOAA" the value of the NOAA Study Name, respectively

1. populates the value of the LiPD metadata NOAAStudyName tag
2. populates the value of the NOAA WDS-Paleo Template Study_Name tag
3. populates the very first line of the NOAA WDS-Paleo Template and is preceded with a “#” (hash character) followed by a space

Request & Bug Report 3. Add Playground support for multiple "Online Resource Description" fields, and Support for a "Description" field to accompany each

1. Request: In Playground, add support for multiple “Online Resource” fields and accompanying “Online Resource Description” fields.

2. Bug report: Playground “Online Resource URL” field and accompanying “Online Resource Description” field, entered by user, are not being output to NOAA WDS-Paleo Template. And extraneous Online Resource and Online_Resource_Descriptions fields from the PAGES 2k V2 project are being output to the NOAA WDS-Paleo Template.

3. When outputting NOAA WDS-Paleo Template, please change “Online_Resource_Description” field name to “Description” in the NOAA WDS-Paleo Template

Request and Bug Report 4. Origninal_Source_URL

1. Bug report: In Playground, when user enters Original Source URL, it is not output to the NOAA WDS-Paleo Template or the LiPD

2. Request: In the Playground NOAA section, add “Original Source URL Description” field and output its value to the Original_Source_URL_Description tag in the NOAA WDS-Paleo Template.

Example snippet form NOAA WDS-Paleo Template: Original_Source_URL: https://www.ncdc.noaa.gov/paleo/study/18077 Description: NOAA WDS-Paleo dataset Landing Page

B. Section Geography Field: NASA GCMD Location (which displays when (NOAA (Beta)) is selected/active

Request 5. Replace the content of the NASA GCMD Location help pop-up with the following content:

Use the GCMD Keyword Valids from https://wiki.earthdata.nasa.gov/display/CMR/GCMD+Keyword+Access Example OCEAN>ATLANTIC OCEAN>NORTH ATLANTIC OCEAN>BALTIC SEA

Request 6. When user selects "download NOAA", populate the NOAA Template "Location" field with the full, delimited GCMD location

For example:

Site_Information Site_Name: Baltic Sea Location: OCEAN>ATLANTIC OCEAN>NORTH ATLANTIC OCEAN>BALTIC SEA Country:

(Note: it is not necessary to populate the County: tag)

C. Section Root Request 7. We don’t understand meaning/intent of the “Created by” field Should it be “Created for”, as in created for a certain repository?

II. Paleo Data Section

Requests for this section have to do with the fields of the columns of LiPD Measurement Tables, which relate to PaST terms (the purpose of which are to describe what was measured).

Background Information: PaST is WDS-Paleo's controlled vocabulary which describes what was measured in terms of a “short name” and ten components: what, material, error, units, seasonality, data type [formerly archive], detail, method, data format [C, or N], and additional information).

For NOAA WDS-Paleo contributions, the “short name” and the ten components (above) describe each column of a LiPD measurement table, although all ten might not apply and be populated for every column. The Playground allows the user to enter the “short name” and three of the ten components: Variable Name (maps to NOAA WDS-Paleo Template “short name”), Description (maps to NOAA WDS-Paleo Template “what”), Data_Format (maps to NOAA WDS-Paleo Template “data format”), and Units (maps to NOAA WDS-Paleo Template “units”). And correctly outputs them to the LiPD and NOAA WDS-Paleo Template it creates.

Specific requests:

Request 8. Add a "NOAA" section to the "Additional fields" section, for each column of each measurement table, which contains seven fields not currently provided by default (listed below in blue)

Importance of this Request 8. and Request 9. (below): This section will allow users to enter information for seven fields which are not currently included in the "Additional fields" (for each column) by default, without having to potentially create up to seven fields (each of which includes correctly entering the field name) that they want to fill in for each measurement table column; User addition of up to seven fields to every column of the measurement table is tedious and error-prone, which would have the unfortunate side effect of making the user less likely to contribute this information and/or have to make modifications/adding content to the resulting NOAA Template.

The seven fields to be added to a "NOAA" section to the "Additional fields" section of the playground are: measurementMaterial (maps to WDS-Paleo PaST "material") error (maps to WDS-Paleo PaST "error") NOAASeasonality (maps to WDS-Paleo PaST "seasonality") NOAADataype* (maps to WDS-Paleo PaST "data_type" (formerly Archive)
(Note greater than one NOAADataType may be entered - each separated by a semicolon)) detail (maps to WDS-Paleo PaST "detail") measurementMethod (maps to WDS-Paleo PaST "method") notes (maps to WDS-Paleo PaST "additional_information")

By Playground design, all “Additional fields” are output to the LiPD file created, associated with the appropriate measurement table field metadata (nice!).

• However note: of the seven fields specified above, three are not currently translated from LiPD to the NOAA WDS-Paleo Template: error, NOAASeasonality, NOAADataType. And this is because we’ve never ask you to do so (spoiler alert, see Request 9.) .

Request 9. Translate the three fields, which are currently not translated from the Playground and LiPD, to the NOAA WDS-Paleo Template.

In the translation of Playground fields and LiPD to a NOAA WDS-Paleo Template, translate measurement table column fields NOAASeasonality to the corresponding PaST “seasonality” component in the NOAA WDS-Paleo Template error to the corresponding PaST “error” component in the NOAA WDS-Paleo Template and NOAADataType to the corresponding PaST “data type” component in the NOAA WDS-Paleo Template

III. LiPD translation request not associated with any section

Request 10. Unless the LiPD creation function is given a base-path where the Template to be created lives, do not output the “WDSPaleoURL” tag to the LiPD output.

[chrismheiser]

I went through the list. I have implemented some of the changes (only on test server so far) and came up with a list of feedback for NOAA.

Request 0 We need tooltip descriptions for the following fields; A hint as to what information is needed from the user for each. For example, “datasetDOI” has the tooltip of "What is the digital object identifier associated with the dataset? Example: 10.1000/sample123” earliestYear mostRecentYear timeUnit onlineResource onlineResourceDescription originalSourceUrl originalSourceUrlDescription modifiedDate datasetDOI NOAADataType NOAAStudyName NOAASeasonality measurementMaterial Error detail measurementMethod NOAAdataFormat

Request 1 What are the available options for NOAADataType? Controlled Vocabulary Tooltip for “NOAADataType” field, also noted in Request 0

Request 2 Tooltip for “NOAAStudyName” field, also noted in Request 0

Request 3 Chris TODO: Make this work for multiple fields and multiple outputs The pages2k links and resources are hard-coded into the output. This is why onlineResource data, and the like, are not being output to the NOAA text files. This was simpler and faster to do when we did the batch processing of the pages2k files. I can change this, but I need to know how to change it. Are the users expected to know the “Online Resource Url” on their own? Are the URLs programmatically created by us? If so, how and with what format?

Request 4 Chris TODO: Make this work for multiple fields and multiple outputs Same issue as above. Currently hard-coded to pages2k

Request 5 Tooltips are simple strings. The URL link will not be clickable and the description does not wrap to a new line. Whole description is on one line.

Request 6 No issues

Request 7 “Created By" is meant to track the origination of the file. We want to know where/how the file was made so that if there are issues with the file, we can know where to look to find out the source of the problem. (i.e. is there a bug with the website, lipd utilities, or something else?)

Request 8 Placing a NOAA section into each column wouldn’t work very well for the current setup of the column data. There’s already a lot of information crammed into each column. However, since I already add in NOAA fields to the columns when the “NOAA Ready (Beta)” switch is turned on, it’s very simple to add the additional 7 of 10 fields at that point. This cuts out the problem of possible errors on entry and the user doesn’t have to do anything extra.

Request 9 No issues

Request 10 Not entirely sure what you’re requesting. What lipd creation function and what base-path? Can you explain futher?

[wendy144]

Request 0 I am working on all tooltips

Request 1 What are the available options for NOAADataType?

Wendy's Response:

Borehole Climate Forcing Climate Reconstructions Corals and Sclerosponges Fauna Fire History Historical Ice Cores Insect Instrumental Lake Levels Loess Paleoceanography Paleoclimatic Modeling Paleolimnology Plant Macrofossils Pollen Speleothems Tree Ring Other Collections

Request 3 Chris TODO: Make this work for multiple fields and multiple outputs The pages2k links and resources are hard-coded into the output. This is why onlineResource data, and the like, are not being output to the NOAA text files. This was simpler and faster to do when we did the batch processing of the pages2k files. I can change this, but I need to know how to change it. Are the users expected to know the “Online Resource Url” on their own? Are the URLs programmatically created by us? If so, how and with what format?

Wendy's Response:

Users are not expected to know, and the Playground should not create any part of the “Online Resource Url”. The user will only enter the URL Domain and Path if NOAA WDS-Paleo provides it. As per a tool-tip, the user will be instructed to contact paleo@noaa.gov to obtain the URL Domain and Path for their file. When the user contacts paleo@noaa.gov, these details will be decided and provided.

Request 7 “Created By" is meant to track the origination of the file. We want to know where/how the file was made so that if there are issues with the file, we can know where to look to find out the source of the problem. (i.e. is there a bug with the website, lipd utilities, or something else?)

Wendy's Response:

In this case NOAA should not be included in the drop-down list, as NOAA will not be creating LiPD files and its presence may cause confusion for a user who wishes to contribute data to NOAA. Question, if file is created by the Playground should they choose lipd.net? I’m pretty sure the answer is yes, just checking

Request 8 Placing a NOAA section into each column wouldn’t work very well for the current setup of the column data. There’s already a lot of information crammed into each column. However, since I already add in NOAA fields to the columns when the “NOAA Ready (Beta)” switch is turned on, it’s very simple to add the additional 7 of 10 fields at that point. This cuts out the problem of possible errors on entry and the user doesn’t have to do anything extra.

Wendy's Response: We like your solution.

Request 10 Not entirely sure what you’re requesting. What lipd creation function and what base-path? Can you explain further?

Wendy's Response:

This appears not to be a problem. For the North American Hydro 2k PAGES study a LiPD JSON-LD field named “WDSPaleoURL” was output. However, now as of Nicks most recent contribution from his publication: The Onset and Rate of Holocene Neoglacial Coolingin the Arctic, GRL, 2018, this field is not being output. Therefore, it looks like this is not a problem. If I see it again, I’ll let you know.

[chrismheiser]

Thanks for the update. I'll add in these items and report back.

[chrismheiser]

It looks like all the requests are done except for the tooltips. I'll keep this issue open a bit longer and wait to receive them.

[wendy144]

Hello Chris, I'll get tooltips to you by Wednesday. Is the most recent executable code available to the public, me included. Best, Wendy

Wendy S. Gross IT Specialist and Data Manager - Paleoclimatology Group Product Lead - World Data Service for Paleoclimatology NOAA's National Centers for Environmental Information (NCEI) Center for Weather and Climate (CWC) 325 Broadway, E/CC23,Boulder, CO 80305-3328 Wendy.Gross@noaa.gov First.Last@noaa.gov

On Fri, Apr 19, 2019 at 5:17 PM Christopher Heiser notifications@github.com wrote:

It looks like all the requests are done except for the tooltips. I'll keep this issue open a bit longer and wait to receive them.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrismheiser/lipdnet/issues/58#issuecomment-485035893, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOHCX7YJRDWUB6Q4LHOR73PRJHJNANCNFSM4GBI34AA .

[chrismheiser]

Wendy, by executable code do you mean the website? If so, yes. It's up to date on lipd.net/playground

[wendy144]

Wonderful! Thanks, Wendy

Wendy S. Gross IT Specialist and Data Manager - Paleoclimatology Group Product Lead - World Data Service for Paleoclimatology NOAA's National Centers for Environmental Information (NCEI) Center for Weather and Climate (CWC) 325 Broadway, E/CC23,Boulder, CO 80305-3328 Wendy.Gross@noaa.gov First.Last@noaa.gov

On Mon, Apr 22, 2019 at 4:48 PM Christopher Heiser notifications@github.com wrote:

Wendy, by executable code do you mean the website? If so, yes. It's up to date on lipd.net/playground

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrismheiser/lipdnet/issues/58#issuecomment-485578975, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOHCXYNYZYYB56UGXIYCULPRY6E3ANCNFSM4GBI34AA .

[wendy144]

Hello Chris, Tool-tip information follows. I also have two comments/questions in red font. Thanks, Wendy

earliestYear

Oldest year in the "timeUnit" specified.

mostRecentYear

Latest year in the "timeUnit" specified.

timeUnit

A unit which is a standard measure of the dimension in which events occur in sequence; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

*User must enter: year Common Era | calendar year before present (where 1950 is present | *radio carbon year before present (where 1950 is present)

Question for Chris: - would it be possible to make this a drop down list of the three items above?

• In a drop-down list "where 1950 is present" would be displayed, but not output to the resulting LiPD or NOAA Template.*

onlineResource

For details request the "NOAA LiPD Guide" via email paleo@noaa.gov.

onlineResourceDescription

For details request the "NOAA LiPD Guide" via email paleo@noaa.gov.

originalSourceUrl

For details request the "NOAA LiPD Guide" via email paleo@noaa.gov.

originalSourceUrlDescription

For details request the "NOAA LiPD Guide" on email paleo@noaa.gov.

variableName

Description of what was measured; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

Question for Chris: - This field was not on your list – however a tool-top would be valuable. This field maps to the required “What” component of the PaST thesaurus. Therefore, it’s important for this tool-tip to appear when “NOAA-Paleo” mode is selected. Is this possible

measurementMaterial

Material(s) on which measurements were made or from which reconstructions were created; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

Error

Use ONLY for data series that are measurements of uncertainty or error; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

Units

Units of measurement; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

NOAASeasonality

The specific part of the annual cycle explicitly reconstructed from raw values; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

NOAADataType

Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

detail

Information about alterations or transformations made to the raw data; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

measurementMethod

Provide techniques, methods, procedures, or strategies for collection or analysis of scientific information; Controlled values are required, request the "NOAA LiPD Guide" via email paleo@noaa.gov.

NOAAdataFormat

Enter the character "N" if data are numeric or "C" if data are character-based.

modifiedDate

Defines the date this dataset was last modified, entered as YYY-MM-DD.

datasetDOI

Enter the Digital Object Identifier associated with this dataset, if one exists.

NOAAStudyName

Describe Where, When and What - e.g. Fort Stanton Cave, New Mexico 55-11kY Speleothem d18O Data.

Wendy S. Gross IT Specialist and Data Manager - Paleoclimatology Group Product Lead - World Data Service for Paleoclimatology NOAA's National Centers for Environmental Information (NCEI) Center for Weather and Climate (CWC) 325 Broadway, E/CC23,Boulder, CO 80305-3328 Wendy.Gross@noaa.gov First.Last@noaa.gov

On Fri, Apr 19, 2019 at 5:17 PM Christopher Heiser notifications@github.com wrote:

It looks like all the requests are done except for the tooltips. I'll keep this issue open a bit longer and wait to receive them.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrismheiser/lipdnet/issues/58#issuecomment-485035893, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOHCX7YJRDWUB6Q4LHOR73PRJHJNANCNFSM4GBI34AA .

[chrismheiser]

I have all these tips added to the page. I cannot push these changes live yet, but I'll update when I do.

[wendy144]

Hello Chris, Apologies, but I have changes to the tool-tip and the list of values to be displayed for "time unit".

"Time Unit" Tooltip: A unit which is a standard measure of the dimension in which events occur in sequence (where applicable, 1950 CE is present).

Values to be displayed in drop-down list: billion years ago calendar kiloyear before present calendar year before present million years ago radiocarbon kiloyear before present radiocarbon year before present year Common Era

I am now methodically testing all of my requests for the Playground, including conversions to LiPD and the NOAA Template. I'll be out of the office starting this afternoon 4/25/2019, so I will start testing today and finish when I return on 5/6/2019.

Best regards, Wendy

On Thu, Apr 25, 2019 at 11:25 AM Christopher Heiser < notifications@github.com> wrote:

I have all these tips added to the page. I cannot push these changes live yet, but I'll update when I do.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrismheiser/lipdnet/issues/58#issuecomment-486764329, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOHCXZRKX2K5VG7TFGJSBTPSHSQNANCNFSM4GBI34AA .

[chrismheiser]

Updates pushed to the website. Feel free to check when you have time.

[wendy144]

SECTION "NOAA" Time Unit tool-tip and drop-down list looks great!

I messed up the tool-tip text for Most Recent Year, apologies - this was my bad Most Recent Year needs to be changed to: Youngest year in the "time unit" specified This will make the tool-tip analogous with "Oldest year ..." tool tip for Earliest Year.

I'll test all others when I return on May 6th.

Today: 2019-0425 - I started testing WDS-Paleo "Requests" from Nov 1, 2018, and capabilities in general, starting with Plaground LOAD and ROOT sections.

---

I. ISSUES FOR LOAD AND ROOT SECTIONS OF PLAYGROUND

---

2019-0425 Issue A. BUG - Toggle NOAA Ready (Beta) response seems reversed. When user turns it on, message displays: Validation is no longer using NOAA rules. When user turns it off, message displays message which indicates it is on.

2019-0425 Issue B. Collection Name QUESTION: What is this tag used for in LiPD, and how does it differ from "Dataset Name"? REQUEST: Add a tool-tip to clarify. Note: NOAA Template does not currently use this tag. Should it use this tag rather than "Study Name" (Under the NOAA section) . Does it serve the same purpose? - if so, it would be best to use it for LiPD and NOAA. The NOAA "Study Name" tool-tip follows: Describe Where, When and What, e.g., Fort Stanton Cave, New Mexico 55-11kY Speleothem d18O Data

2019-0425 Issue C. Investigators REQUEST: request that Playground check the formatting of "investigators" filed in order to facilitate accurate parsing in downstream apps. Format is: LastName, FirstName; Lastname, FirstName;...

2019-0425 Issue D. "notes" REQUEST: request that Playground add tool-tip when "NOAA Ready (Beta)" is turned on for "notes". Following is the tool-tip for NOAA. Please use it when user selects "NOAA Ready (Beta)" or use it in general if it works for both LiPD and NOAA Template. Text for tool-tip: Anything that you would like the user to know about this dataset, including keywords. Anything you cannot fit somewhere else and want to document.

---

II. CROSS-WALK PLAYGROUND ROOT SECTION OF PLAYGROUND Note to Chris: Here I have documented the cross-walk of all fields from Playground to LiPD to NOAA Template for the ROOT Section.

---

Column Descriptions: PLAYGROUND/LIPD/NOAA TEMPLATE

LiPD Version/lipdVersion/NOT APPLICABLE

Dataset Name/JSON TOP LEVEL "dataSetName"/Data_Collection Collection_Name

Created By/JSON TOP-LEVEL "createdBy"/NOT APPLICABLE*

Archive Type/JSON TOP LEVEL "archiveType"/NOT APPLICABLE*

• Note: in this case going round-robin from LiPD->NOAA Template->LiPD will not be possible. Concern: "archiveType" is required for a valid LiPD

  Collection Name/JSON TOP-LEVEL "collectionName"/NOT APPLICABLE*

• Note: in this case going round-robin from LiPD->NOAA Template->LiPD will not be possible. Concern: "collectionName" is required for a valid LiPD

  Investigators/JSON top-level "investigators"/Investigators Note:Playground tool-tip - Use the format: LastName, FirstName; Lastname, FirstName;

  Notes/JSON Top-level "notes"/Description_Notes_and_Keywords Description:

Wendy S. Gross IT Specialist and Data Manager - Paleoclimatology Group Product Lead - World Data Service for Paleoclimatology NOAA's National Centers for Environmental Information (NCEI) Center for Weather and Climate (CWC) 325 Broadway, E/CC23,Boulder, CO 80305-3328 Wendy.Gross@noaa.gov First.Last@noaa.gov

On Thu, Apr 25, 2019 at 4:50 PM Christopher Heiser notifications@github.com wrote:

Updates pushed to the website. Feel free to check when you have time.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chrismheiser/lipdnet/issues/58#issuecomment-486865371, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOHCXYUJURYCYHTO5N7TWDPSIYUZANCNFSM4GBI34AA .

[chrismheiser]

The tooltip for timeUnit is updated.

2019-0425 Issue A. I'm not seeing this issue. Do you have specific steps to replicate it or is this directly after loading a new page? 2019-0425 Issue B. Let me check with Nick on the Collection Name. I don't see it often, and the times that I do remember seeing it, it was similar or identical to the dataSetName. I think I meant for it to map to the "Data_Collection > Collection_Name" in the NOAA Template, but on the playground it's in a different section. It may need to be moved to the NOAA section. 2019-0425 Issue C. I'll try to find a way to check the string formatting, but likely the formatting will be up to the user to get correct. 2019-0425 Issue D. There's not a way to split tooltips between modes, but I'll put your text for "notes".

Section II Are these items not currently mapped correctly? I'm also confused by the "Column Descriptions:" being above all the root level items.

[wendy144]

You wrote: The tooltip for timeUnit is updated. Tooltip looks good. However, the drop-down list of choices for the "Time Unit" is gone. It should contain the following values: billion years ago calendar kiloyear before present calendar year before present million years ago radiocarbon kiloyear before present radiocarbon year before present year Common Era

2019-0425 Issue A. Steps to replicate issue Operating System - Windows 7. I am seeing the same results for Firefox and Chrome. In short whenever "NOAA Ready (Beta)" is selected, the following dialog displays: "Fields may be ignored Validation is no longer using NOAA Rules", regardless of whether page loading is a new page.

Browser Versions: Google Chrome is up to date Version 74.0.3729.131 (Official Build) (64-bit); Firefox is up to date Version 66.0.5 (64-bit)

Test Cases: Note: The same results occur regardless of whether: (1) I do NOT clear history and data prior to loading a new page; or (2) I clear history and data prior to loading a new page. Test Case One - Step 0: Launch Browser Window; Step 1: Navigate to lipd.net/playground; Step 2: Upload LiPD file; Step 3: Select "NOAA Ready (Beta)"; Results: Dialog displays: "Fields may be ignored. Validation is no longer using NOAA Rules." Test Case Two - Step 0: Launch Browser Window; Step 1: Navigate to lipd.net/playground; Step 2: Select "NOAA Ready (Beta)"; Results: Dialog displays: "Fields may be ignored. Validation is no longer using NOAA Rules."

2019-0425 Issue B. Let me check with Nick on the Collection Name. I don't see it often, and the times that I do remember seeing it, it was similar or identical to the dataSetName. I think I meant for it to map to the "Data_Collection > Collection_Name" in the NOAA Template, but on the playground it's in a different section. It may need to be moved to the NOAA section.

"Dataset Name" in Playground maps to dataSetName in LiPD, which has always mapped to "Data_Collection >Collection_Name" in the NOAA Template. This behavior is fine, Name.Location.Year, is a suitable NOAA Template "Data_Collection >Collection_Name". I no longer see "Collection Name" field in the Playground ROOT section.

It is fine with us to leave "Collection Name" out of Playground all together. "Study Name", is a better choice than "Collection Name" in the NOAA section.

2019-0425 Issue C. I'll try to find a way to check the string formatting, but likely the formatting will be up to the user to get correct. Okay.

2019-0425 Issue D. There's not a way to split tooltips between modes, but I'll put your text for "notes". Okay.

Section II You wrote - Are these items not currently mapped correctly? I'm also confused by the "Column Descriptions:" being above all the root level items.

The items (fields) for the ROOT section are mapped correctly. What I was trying to do here is create a table which shows the mapping from Playground to LiPD to NOAA Template, and the "Column Descriptions" depicted the header for each of the three columns. This has not worked, instead, I will create a google-sheet and place the URL for it in this GitHub ticket.

[wendy144]

Hello Chris, I have created google sheet: PLAYGROUND-LIPD-NOAA-TEMPLATE-XWALK and I have shared it with you. I'm going to continue testing Playground to LiPD to NOAA Template and keep adding to this document. My plan is to finish testing and and reporting issues withing this next week. Cheers, Wendy

[chrismheiser]

TimeUnit: The dropdown is working, but with a caveat. There is a bug with angular dropdowns, so I use autocomplete dropdowns instead. The dropdown list displays when the field is still blank or when your current typing matches one of the options.

2019-0425 Issue A. Steps to replicate issue I have tried Safari, FireFox, and Chrome on both MacOS and Windows 10 with current versions of the browsers. I do not have a copy of Windows 7 to attempt on. All of the above attempts worked normally. I don't know if it's possible to take a screen recording of the bug, maybe that would help, but I'm unable to recreate it currently.

2019-0425 Issue B Collection Name is removed.

2019-0425 Issue C I'm going to add in a rule that checks for semi-colon separated strings and reports a warning if it thinks the investigators are improperly formatted. This will still largely be up to the user to get correct based on the tooltip information, but the warning may help too.

[wendy144]

2019-0425 Issue A. Steps to replicate issue I am able to recreate the problem on Windows 10. I do not have the capability to do a screen-recording, however I can invite you to a google-hangout and share my screen.

[wendy144]

2019-05 Issue A. Section Online Resource: When user clicks on "+ Online Resource" nothing happens. No "Online Resource 1" box which will enable user to enter the resource and description, is displayed.

[wendy144]

2019-05 Issue B. Section Funding: When a Funding record is entered via Playground, an extra "blank" Funding record is placed in the LiPD exported, and the NOAA Template exported. For example:

{ "agency": "", "grant": "", "investigator": "", "country": "" }

[chrismheiser]

2019-0425 Issue A. Steps to replicate issue That may be possible. I would also try emptying the cache of the browser if you can. I know you deleted history, but I don't know if that included the cache also.

2019-05 Issue A. I'm also unable to recreate this issue. There seems to be something weird going on with your environment. I'm going to see if anyone else can recreate these issues.

2019-05 Issue B. I was able to recreate this. I'll work on a fix for it.

[wendy144]

For 2019-0425 Issue A. and 2019-05 Issue A. I did empty the cache of the browser as well as the history.

[wendy144]

2019-0531 Issue A. On Nov 6, 2018, Chris Heiser wrote: Request 8 Placing a NOAA section into each column wouldn’t work very well for the current setup of the column data. There’s already a lot of information crammed into each column. However, since I already add in NOAA fields to the columns when the “NOAA Ready (Beta)” switch is turned on, it’s very simple to add the additional 7 of 10 fields at that point. This cuts out the problem of possible errors on entry and the user doesn’t have to do anything extra. To which Wendy responded: We like your solution

Comment from Wendy gross May 31, 2019 I don't see that this has been implemented. Am I missing something

Note that today (2019-0531) I now see that "measurementMaterial" is included in the Playground Datatable Column Additional Fields, and is placed in the NOAA Template "material" for a field (measured variable). Therefore, there are six "Additional Fields" that need to be added to Playground. These six follow along with notes about cross-walk from Playground to LiPD to NOAA Template:

1. error - Needs to be put into LiPD as JSON metadata for the field of a data column. It maps to WDS-Paleo PaST variable component "error" in the NOAA Template.

2. NOAASeasonality - Needs to be put into LiPD as JSON metadata for the field of a data column. It maps to WDS-Paleo PaST variable component "seasonality" in the NOAA Template)

3. NOAADataype - Needs to be put into LiPD as JSON metadata for the field of a data column. It maps to WDS-Paleo PaST variable component "data_type" in the NOAA Template (Note 1: it was formerly named "Archive".) (Note 2: greater than one NOAADataType may be entered - each separated by a semicolon.)

4. detail (maps to WDS-Paleo PaST variable component of "detail" in the NOAA Template)

5. measurementMethod (maps to WDS-Paleo PaST "method" in the NOAA Template)

6. notes (maps to WDS-Paleo PaST "additional_information" in the NOAA Template)

[wendy144]

2019-0531 Issue B. Playground GEOGRAPHY Section I have three concerns/request for when geographic coordinates are specified as Degrees Minutes Seconds

1. In NOAA Template generated, they are not converted to decimal degrees. Instead Northernmost_Latitude, Southernmost_Latitude, Easternmost_Longitude, Westernmost_Longitude are all set to whatever was entered in the in the "decimal degrees" screen.

2. In the LiPD generated, tags: "geometry>coordinates" are not converted to decimal degrees. Instead they are set to whatever was entered in the "decimal degrees" screen (which will be zero by default - if the user did not enter anything)

3. When "NOAA Ready" is turned on, it would be simpler just to force the user to enter decimal degrees.

[wendy144]

2019-0531 Issue C. Playground GEOGRAPHY Section - I request that you change "Decimal Degrees" to "Decimal Degrees (WGS84) thereby specifying the horizontal datum, and letting the user know the geographic coordinates must be entered as WGS84. Note that the horizontal datum for WGS84 is the default for GeoJSON - which is the standard LiPD uses. However, the end-user does not know that LiPD is using GeoJSON and what it really means to do so.

[wendy144]

2019-0531 Issue D. Playground GEOGRAPHY Section - For Units (of Elevation), when "NOAA Ready" is turned on, the value for Units should be not-editable by the user and set to Meters - because for NOAA Template, it has to be meters.

I think this is the case, please confirm that it is.

[wendy144]

2019-0531 Issue E. Playground GEOGRAPHY Section When geographic coordinates are specified as Degrees Minutes Seconds there are problems: A. In NOAA Template generated, they are not converted to decimal degrees. Instead Northernmost_Latitude, Southernmost_Latitude, Easternmost_Longitude, Westernmost_Longitude are all set to whatever was entered in the in the "decimal degrees" screen. B. In the LiPD generated, geometry>coordinates are not converted to decimal degrees. Instead they are set to whatever was entered in the Playground "decimal degrees" screen contains. C. Suggestion/Request: when "NOAA Ready" is turned on, it would be simpler just to force the user to enter decimal degrees.

[wendy144]

2019-0531 Issue F. Playground PUBLICATION Section: Three fields in Playground are not output to LiPD or NOAA Template, and they need to be. These are: Report Edition Citation Please see document: PLAYGROUND-LIPD-NOAA-TEMPLATE-XWALK at URL https://docs.google.com/spreadsheets/d/1xl9ptsY15qkNauWLt-Dh_4yNcqS-y-2dEhXqg_-pcCY/edit#gid=0 for crosswalk from Playground to LiPD to NOAA Template

[wendy144]

2019-0531 Comment/Kudos from Wendy - I have now finished exploring the entire Playground in the state when "NOAA Ready" is selected, and look forward to working with you to resolve the issues I've found. Playground is a very well thought out, powerful app. Much thanks for all of your hard work and help! Cheers, Wendy