mattbk / nodakpaleo Goto Github PK

Consider https://www.drupal.org/project/flag_lists, to let people make private lists of localities or specimens. Add mapping? This is a way to get around using regular queries to select nodes, but there definitely needs to be a way to pro grammatically select the nodes you want.

Right now we can do this with Projects, but that involves directly editing the nodes themselves.

http://drupal.org/project/geofield

Maybe with OpenLayers instead of GMap.

Yes. See Evernote for plans on 2015-01-11:

Should use Geofield instead of the Coordinates system I have set up. Then the location is tied to the Locality node, not a separate node. As long as I can include multiple Geofield entries per node. Is there way to Geofield query in Views by selecting from map?
Will need to convert from GMap to OL, too. Did I turn off GMap?
Looking at any data in Location module fields, then can hopefully get rid of that module. There are data, install Geofield and move data over: http://nodakpaleo.mattbk.com/old-locations-list. Then do the same with Coordinates nodes: http://nodakpaleo.mattbk.com/coordinates.

See the list of tickets from the old system at

• http://nodakpaleo.mattbk.com/tickets
• http://nodakpaleo.mattbk.com/support/nodakpaleo
• Evernote

I'm not copying everything over just now because there are a lot of active ones . . .

Would especially help for documentation.

Create a Feeds import to allow easy import of multiple specimens.

I don't trust Feeds entirely to not create duplicates if someone hasn't already QCed duplicates out of the import dataset, but that's something that will have to be dealt with. The Paleobiology Database has a great deal of documentation for QA/QC when importing, so I don't think it's too much to ask for people to do the same for NodakPaleo.

Create a "to do" list where anyone can get started, do some research, and provide feedback that can be incorporated into the database. E.g., figuring out the taxa in "AA Possible Error," etc.

Helps if anyone downloads the image and doesn't label it properly.

When geofield is empty, hide the whole map. Not sure how to do this, filter in views doesn't seem to work.

Get on the export functionality!

Consider
Views Data Export requires a new view to be created that has all the fields that you want o export, so it's not the most versatile. What we really need is a node export system that includes all fields by default.

Really what people want from Views is a way to export the nodes shown in the Views, not just the data they are currently seeing. Trying out Node Export. Might also needhttp://drupal.org/project/views_bulk_operations

This is going well for the one-off things like exporting a single locality or specimen from the node view, especially since I got flipped tables to work. Need to build this into the views that list more than one node at a time next.

Permissions
__Don't forget to make sure that only truncated position fields are exported for Coordinate nodes.

Ugh. This will be some work.

Key: how to obfuscate locations for people without correct permissions?

• Map of all localities
• Map of all coordinates
• Map for each locality, showing associated coordinates
• Map for each specimen, showing associated locality
• Map attached to each major query type, showing results (like Northern Plains Athletics)

This is a good start: http://www.protichnoctem.com/nodakpaleo/?q=maps/specimen
Add some exposed filters (see existing simple specimen search) and figure out how to attach a table to the map view.
Make a view for each of precise and obfuscated specimen positions.

Obfuscation at the moment is through field permissions: only admin and researcher roles have access to see precise lat/long and UTM coordinates.

I am looking into showing both precise and truncated coordinates on the same map and then letting field permissions show points depending on what people are allowed to see. This is holding me up: http://drupal.org/node/1290534

At the moment, though, you can create two maps with different permissions (view field_latitude or view fields_latitude_trunc) and that will determine which map to show (unless a user has both permissions, which would be silly). In use on this page: http://www.protichnoctem.com/nodakpaleo/?q=node/2550/localities

Converting to Geofield and OpenLayers should solve these problems.

List ideas for queries here. Plan how to build a query library.

• Specimen by stratigraphy and classification. Map returned specimens.

I have fixed this for now by adding the field as a teaser rather than the official biblio citation plugin.

At the moment, using the method in #4 of this thread but would like to use the method in #2 since I'm already using Computed FIelds.
http://drupal.org/node/710840#comment-5498938

Here is the Rule: http://www.protichnoctem.com/nodakpaleo/?q=admin/config/workflow/rules/r...

Working on making a View that lists specimen numbers and the QR code so a batch can easily be printed out based on filter criteria.

It's hard to print out a bunch at a time (http://www.protichnoctem.com/nodakpaleo/?q=print-mobile-codes; Researcher menu) because certain browsers will split the rows or split the images across page breaks. Trying to figure out a solution for this.

See #2812

I am leaving these for now, but I've noticed that some of them have the wrong URL and should be bulk updated in the future when there is a solid domain name.

As work with specimens increases, so should the number of photos available. Add a field for extra photos.

Probably revamp taxonomy term pages to make them easier to digest. Retain ability to list all full nodes (if someone wants to print, maybe?).

Also loses all data in add node form when you do this.

Best way to add new specimens.

Also sucks to have to search by title when citing.