Blattodea Culture Group

Only first 10 references shown in reference field, often having nothing to do with real citation. This make it impossible to attach any biblio references

I noticed that on a site (http://aframomum.myspecies.info/) the updates on the darwincore module have not been running since october 2012, because update 7005 failed. That's now fixed - but the problem is that this site's updates have been failing for a while, and it wasn't detected.

Aggregate data from lower taxa to parent taxa overview pages.

References, specimen records and images should be aggregated at the next higher taxon level.

For example when I am looking for specimens of a genus it is obvious that I want to see all the specimens identified as lower taxa of this genus (species and below). This could be given as an option on taxonomy settings.

However, taxon descriptions and nomenclature content types should be excluded from this process.

No unpublished content should be present in the DwC-A

'Archive' is misspelled on "The Darwincore Arhive for this site has not yet been created". See attached screenshot

I received an e-mail saying a "security update available for your version of Drupal", with two links provided. However I am denied access for both the links (..myspecies.info/admin/reports/updates and ..myspecies.info/admin/reports/updates/settings). Is this update handled by someone other than the maintainer of the site?

Tasks and bugs associated with Kemu and Imu

Write SCAN documentation

Imu access to SCAN tables

It would be great to allow weights to be selected on taxon descriptions and in this way allow users to choose the order in which descriptions get displayed on a taxon page with numerous different descriptions. See http://potamogetonaceae.e-monocot.org/taxonomy/term/398/descriptions for example

Users need to be able to order the collectors they add to a Specimen/Observation. This is needed for (at least) the publication module.

The way to do this is to change the widget from a select list to a user reference. This would be an great UI improvement, as selecting multiple contributors is currently difficult.

Document the use of resource url content type and taxonomies

Write views table css such that the web resource url pages such that the tables, rows or cells can be styled in a variety of manners through the use of custom css

In the literature, the authors name appears correctly in the BIBLIO:AUTHOR facet. They don’t display in the same way in the Literature table.
For example: ‘APG, The Angiosperm Phylogeny Group’ displays as ‘APG, TAngiosperm’ in the table.
I have tried editing the name in the editor, but it seems to make no difference.

I would like to upgrade the Entity module from the beta release we are currently using, to the stable 1.0 version. This is quite a major change, which could have knock on effects on many parts of the site. It is therefore prudent to thoroughly test this upgrade before rolling it out. A test site is available at:

http://entity-stable.scratchpads.eu/

Please test it, and list any errors that are experienced on that site that are not experienced on a standard site.

List of features affecting the publication module:
*Author name ordering for specimens
*Required fields in the specimen/observation content type (work-around with cloned content type)
*Grid editor not allowing changes to dates and people in specimen/observation "lite"
*Inconsistent tags for referencing literature [cite] and [bib]
*Replicate the functionality of the new insert options in taxon descriptions, pages and other content types (reference, figure, specimen, table)
*Ampersand rendered as & in article title
*Add reference options to figures and tables

Questions:
*Do we run checks to ensure all references are used in the publication?
*How will we control access to the publication, including making the publication public?
*Should we have a workflow for publications to allow the author/creator to invite people (existing and non-site users) to contribute?

Some of the Scratchpads 1 site use back-references. This allows them to display, within a node page, nodes that reference the current node.

For instance on this page:

http://acoela.myspecies.info/content/1200f

The "Primer Map" at the top is displaying content that holds a reference to the current node. We would like to be able to keep similar functionality when migrating over.

The scratchpads 1 sites use two modules for this:

- Node Relationships which display referencing node content ; and
- Node Referrer which displays a list of referencing nodes.

Node Relationships¶

This module does not have Drupal 7 version, and the related issue does not get much love.

In a way, the 'spiritual' successor of that module would be the Relation module - what Node Relationships wanted to provide was in effect what Relations provides.

Otherwise I have not found a module that provide backreferences in the same way. The Corresponding node references module requires a field on both side of the relation, and most other modules that claim to implement functionality of the Node Relationships module only implement the 'create related content' part of the functionality. There is a Drupal answers question that lists the available module - none of which fit the bill, as they all focus on having a field on both side of the relation ship.

One of the reason no module implements the same functionality is because this can be provided by Views - as is explained on the Reverse Node Reference module page.

NodeReferrer¶

This module does have a beta D7 version, which does provide the same functionality as the Drupal 6 module.

However the functionality required here is very similar to the functionality required by the Node Relationships backreference. It would make more sense to address both problems as one.

Possible Solutions¶

1. Implement this using Relation module. In terms of migration, this would be really complicated. We'd have to detect node reference fields and their counter-part backreference fields - then we'd have to create a Relation type that match those two content type, remove the fields and create a relation in their stead ;

2. Implement this using views. The simplest way would be to provide a block with a view that displays back references, and use context to ensure that block is displayed for the right content types ;

3. Implement our own field that would be the equivalent of Backreference as provided by Node Relations module ;

4. Provide a patch to the node referrer module that provides this functionality.

Vlad has made some suggestions on additional Biblio reference fields that would be useful to other Scratchpad users.

Discuss these suggestions and alter the nomenclature block.

We need to add the Scratchpad style resources to the Scratchpads.eu site as we get periodic requests for a Scratchpads Style Guide for our collaborators to use when creating promotional materials, usually in other countries.

Possibly something like http://build.e-monocot.org/mocks/styleguide.html (screenshots attached).

I am discussing this with Malin and Alice.

Column 6 of the classification.txt file - namepublishedin field is empty when it should contain the protologue information.