Attribute list for export to be chained together

[LeannePyle]

From Collection Event

• [x] Collection Year
• [x] Location Descriptor
• [x] Spatial Coordinates Geometry

From Fossil Sample

• [x] Samples Collected – scientific names if available, or common names
• [x] Size Category
• [x] Repository or Institution Number = Storage Reference
• [x] Minimum Time – ensure something in the hierarchy displays here – if no Epoch, then use Period
• [x] Maximum Time
• [x] Geological Group
• [x] Geological Formation - always show associated higher level of Group if applicable
• [x] Geological Member – always show associated higher level of Formation and/or Group
• [x] Other Stratigraphic Name – if Group, Formation, Member unavailable
• [x] Informal Map Unit – if Group, Formation, Member unavailable

From Publication - for consultants and researchers only, and only for public domain sources

• [x] Title
• [x] Year of Publication
• [x] Journal or Publication Name
• [x] Authors

For Discussion

• [x] Need to identify needs based on export scenarios for EAO vs paleo consultant for industry vs land application - best to create a superset now and work with customizing later
• [x] How will null values display in csv? - these will be blank
• [ ] For spatial information/shapefiles for certain attributes - are these available publicly elsewhere - e.g., protected fossil sites such as McAbee? - if the protected sites are part of the resource model, then this needs to be where the data is available from

Dev Notes

• Data consolidation implemented as a set of views on the base TILES table to extract various parts of the collection event, sample, fossil type, contributors an publication models
• Intercepting the export API endpoint and redirecting to a subclass of the main SearchExport class.
• The sub-class overrides the to_csv function. If the list of instances is a list of Collection Events (CE), uses the list of CE resourceinstanceids to extract the data from the view and then forwards that and the list of view column names back to the parent to_csv method for processing

Questions to answer

• Do we always want to use the alternate collection event export list (which is heavier) or have a separate option for that - BF - yes
• How do we check if the MVs are up to date or not? - For now we are going to start by refreshing them via cron every hour

[bferguso]

First cut complete in Dev. This will likely need some MVs for performance. It takes some time for them to be refreshed before run so we will likely need to modify the export UI to check to see if updates have happened since the last MV fresh, and (b) provide a mechanism to update the MVs prior to performing export.

[bferguso]

@LeannePyle, @elisabethdeom - By including the publication information we may end up having some awkwardly long fields (title), and once again be grouping information that is hard to decipher once it is collated (publication title -> authors, sample -> fossil names)

[bferguso]

Based on our last meeting, we will include a unique list of publication years, publication types and authors. Also included a publication count column.