Wikidata:Property proposal/EPA Ecoregion Level 1 Code
EPA Ecoregion Level 1 Code edit
Originally proposed at Wikidata:Property proposal/Natural science
Not done
| Description | part of a classification system for ecological areas with similar habitat in North America |
|---|---|
| Represents | Level I ecoregion (Q98544667) |
| Data type | External identifier |
| Domain | Level I ecoregion (Q98544667) |
| Allowed values | ([1-9]|1[0-5]) |
| Example 1 | Tundra (Q98825169) → 2 |
| Example 2 | Arctic Cordillera (Q98825182) → 1 |
| Example 3 | Tropical Wet Forests (Q98825183) → 15 |
| Source | https://www.epa.gov/eco-research/ecoregions |
| Planned use | I will create instances of Q98544667 for the 15 identities in this class of ecoregions. See my code here for building the WikiData item information and links for all EPA Ecoregions. |
| Number of IDs in source | 15 |
| Expected completeness | eventually complete (Q21873974) |
| See also |
Motivation edit
User TimK_MSI started creating items for two of the classes of EPA ecoregions some time ago (User_talk:TimK_MSI). Without an identifier property, he incorporated an identifier into some of the items by including a series ordinal on the instance of property in cases like Q5330161. I am now finishing out the work to generate items and linkages for all EPA ecoregion classifications as a persistent, resolvable, online resource for work in my lab and by others who work with these data for various analytical purposes. I would like to put identifiers on each item, properly registered to official properties, such that we can execute queries from external data systems that already have the original EPA Ecoregion codes in use. Skybristol (talk) 14:13, 25 August 2020 (UTC)
Discussion edit
Comment please add three samples to each proposal. --- Jura 15:53, 26 August 2020 (UTC)
- I did add 4 examples of the actual code/identifier values in the template for all 5 of the ecoregion identifiers I proposed. In the case of Level 1 Ecoregions, these really are as simple as the numeric identifiers I included as examples. You can review samples of the items to which these identifiers will apply via this instance of query, where you will see that I've temporarily put a compound form of the identifier into the aliases. The reason we need separate identifier properties for these is not only for proper semantics but also to apply a formatter URL property that will facilitate linking from the items to third party resources such as map server queries to return full boundary geometry for the items. Skybristol (talk) 22:05, 1 September 2020 (UTC)
- Would you insert them in the template? See another proposal on how it's done. --- Jura 22:12, 1 September 2020 (UTC)
- Thanks for pointing me in the right direction on this. I put specific item into the examples as directed. Skybristol (talk) 12:33, 10 September 2020 (UTC)
- Would you insert them in the template? See another proposal on how it's done. --- Jura 22:12, 1 September 2020 (UTC)
- I did add 4 examples of the actual code/identifier values in the template for all 5 of the ecoregion identifiers I proposed. In the case of Level 1 Ecoregions, these really are as simple as the numeric identifiers I included as examples. You can review samples of the items to which these identifiers will apply via this instance of query, where you will see that I've temporarily put a compound form of the identifier into the aliases. The reason we need separate identifier properties for these is not only for proper semantics but also to apply a formatter URL property that will facilitate linking from the items to third party resources such as map server queries to return full boundary geometry for the items. Skybristol (talk) 22:05, 1 September 2020 (UTC)
Support I have also updated the regular expression to be more precise (only 16 values so no need to accept numbers like 1293797) and fixed some minor formatting with the proposal. --Dhx1 (talk) 15:38, 23 September 2020 (UTC)- Comment Domain also changed to ecoregion (Q295469). --Dhx1 (talk) 15:43, 23 September 2020 (UTC)
- Comment Undone as the original domain was more precise and correct. --Dhx1 (talk) 16:06, 23 September 2020 (UTC)
- Comment @Skybristol: I changed the number of items from 16 to 15 per the official website at [1] and the English Wikipedia article that both state only 15 identifiers exist in the series. Can you clarify which is correct before I provide support to this proposal? --Dhx1 (talk) 15:55, 23 September 2020 (UTC)
- Comment The description at [2] indicates this identifier was issued by Commission for Environmental Cooperation (Q2986468) and not United States Environmental Protection Agency (Q460173). I suggest that the name of this property could therefore be "CEC 2006 Ecoregion Level 1 Code" and the source URI/official website becomes [3]. --Dhx1 (talk) 16:37, 23 September 2020 (UTC)
- Comment Is there a reason for making all the levels separate properties? I feel that two properties, "CEC Ecoregion code" linked to (what's the QID?) and "EPA Ecoregion code" linked to United States Environmental Protection Agency ecoregion (Q52111282), will suffice. The levels are pretty obvious from the formatting for both humans and machines.--Artoria2e5 (talk) 06:00, 2 February 2021 (UTC)
- Support, an important property for biology.--Arbnos (talk) 14:59, 19 February 2021 (UTC)
- @Skybristol: -- could you respond to the questions here and on the other associated proposals? I think once you address them, this is probably close to ready. JesseW (talk) 14:30, 28 March 2021 (UTC)
Not done it seems to be stale for quite some time. If there is still interest, it's worth going through the five or so pages and formulate a new proposal with the input there. --- Jura 19:52, 18 November 2021 (UTC)
