To:Isaac Casanovas;Lars van den Hoek Ostende;Zliobaite, Indre
Fri 23/09/2022 14:12
Hi,
I made a "total" export from NOW using a direct SQL query to the database.
I then ordered the columns more or less to be in the same order as the user interface have them in NOW. This export does not have the new archaeology data which will soon be implemented in NOW
On the list you can see five headings on the left:
Entity: Locality or Species
Tab name:
Section name:
Field caption:
Database field:
Then I colour coded the columns:
red (19 fields): data not visible in NOW UI or an id-field
green (14 fields): suggestion for the minimum export field
orange (150 fields): large export fields
yellow (7 fields): needs SQL fiddling, a concatenated field or additional tables for the query, also large export fields
Based on the suggestions, these fields could always be in the export:
Localities:
Name, Country, Minimum Age, Maximum Age
Species (the taxonomy):
Class, Order, Family, Subclass or Superorder, Suborder or Superfamily, Subfamily or Tribe, Genus, Species, Unique Identifier, Taxon Status
I also suggest that we enable the users only select the exported fields at the section level which would limit the number of check boxes to 40 or so instead of the 170+ different fields. Also, all the "green" fields would always be in the export.
I hope this example file of all public data will show you the current data we have and also helps you make some additional suggestions for the basic export.
Any comments welcomed,
-Kari
Activity
Show details
Write a comment…
Kari Lintulaakso Dec 1, 2023 11:28 AM
To:Lintulaakso, Kari-E J;Isaac Casanovas Vilar;+1 other
lid, like the species_id are id-fields. They are in the export.
The duplicate id-values come from the locality species table (SQL select * ... causes that).
I added the coordinates as basic export fields. Also, I noticed that many of the listed fields are not included in the current NOW export (the 'Selected Localities and Species' export), although they are visible in the user interface (for example formation, member, bed). I will meet Indre tomorrow and we could have a quick look at these missing fields.
To:Isaac Casanovas;Lars van den Hoek Ostende;Zliobaite, Indre
Fri 23/09/2022 14:12
Hi,
I made a "total" export from NOW using a direct SQL query to the database. I then ordered the columns more or less to be in the same order as the user interface have them in NOW. This export does not have the new archaeology data which will soon be implemented in NOW
On the list you can see five headings on the left: Entity: Locality or Species
Tab name: Section name: Field caption: Database field:
Then I colour coded the columns:
red (19 fields): data not visible in NOW UI or an id-field green (14 fields): suggestion for the minimum export field orange (150 fields): large export fields yellow (7 fields): needs SQL fiddling, a concatenated field or additional tables for the query, also large export fields Based on the suggestions, these fields could always be in the export:
Localities: Name, Country, Minimum Age, Maximum Age
Species (the taxonomy):
Class, Order, Family, Subclass or Superorder, Suborder or Superfamily, Subfamily or Tribe, Genus, Species, Unique Identifier, Taxon Status
I also suggest that we enable the users only select the exported fields at the section level which would limit the number of check boxes to 40 or so instead of the 170+ different fields. Also, all the "green" fields would always be in the export.
I hope this example file of all public data will show you the current data we have and also helps you make some additional suggestions for the basic export.
Any comments welcomed,
-Kari
Activity Show details Write a comment… Kari Lintulaakso Dec 1, 2023 11:28 AM To:Lintulaakso, Kari-E J;Isaac Casanovas Vilar;+1 other
Thu 29/09/2022 11:31
Sounds good to me.
Indrė
Edit • Delete Kari Lintulaakso Dec 1, 2023 11:26 AM To:Isaac Casanovas Vilar +2 others
Mon 26/09/2022 13:29
Hi,
lid, like the species_id are id-fields. They are in the export.
The duplicate id-values come from the locality species table (SQL select * ... causes that).
I added the coordinates as basic export fields. Also, I noticed that many of the listed fields are not included in the current NOW export (the 'Selected Localities and Species' export), although they are visible in the user interface (for example formation, member, bed). I will meet Indre tomorrow and we could have a quick look at these missing fields.
Any other fields to the basic export?
-Kari
Edit • Delete Kari Lintulaakso Dec 1, 2023 11:24 AM To:Lintulaakso, Kari-E J;Isaac Casanovas Vilar isaac.casanovas@icp.cat;+1 other
Mon 26/09/2022 10:25
Hi,
looks good in principle.
Is "lid" really not visible to the users in the current export? Also "lid" is in B and CL columns, what's the difference?
I think we should give coordinates in the main export, one version of the coordinates, perhaps the decimal?