Metacat

Correction in the previous description. This is not required:

'A new action should be created for moderator login? action=login can not
be used here because Metacat has to be told to check if the user is a moderator
or not. Hence either a new action has to be created. Or a new arguement to the
login action has to be *created.'

Moderators can be handled in the same way as administrators are handled
currently. That is when an action is requested, it can be checked if a user is
moderator or not.

I agree with all of the steps you outlined. However, the layout of the
moderation resultset was discussed as well. We want the moderation process to
be as quick and easy as possible. So we might consider a system where the
moderation form (accept, decline, revise, explanation) is in the EML document
itself (possibly rendered on the left side in its own iframe). When the
moderator makes a decision, he bonks the button and is automatically brought to
the moderation page for the next document.

Moderator UI and functionality for ESA has been implemented. Waiting for
feedback from ESA and next round of changes. Hence, moving the bug 1.7

When checking ESA mail response for Metacat release I notice that the email path has problems on the revise document. Here are too examples:

---------
Dear Callie Bowdish,

Upon review, we feel that the metadata entry for your article submission,
Test ESA edit Mon June 11:37, is still missing some relevant information. Please read the
reviewer's comments below for any suggested additions and changes. You are strongly
encouraged to go back and address these issues with your entry. You can login,
edit, and resubmit your entry at http://chico.dyndns.org/cgi-bin/register-dataset.cgi?stage=modify&cfg=esa&docid=esa.3.

The Ecological Society of America

Reviewer's Notes:
This looks good, Callie. Please add a little more in the methods section.

Callie

The path for some reason does not go to the latest version number even though the "docid=esa.3". Usually when there is not a version number the version goes to the most recent data package. This path opens the data package in the online form but it is name esa.3 with no version number. If the user works with the address posted in the email they will not be able to save because there is already a version older than that one.

I am not sure if this is just on the test server.

The ESA email for when the data package is accepted says:

Dear callie bowdish,

We are happy to inform you that the metadata entry for your article submission,
Test ESA on Chico, has been accepted. This part of the submission process is now
complete. Your metadata entry can be cited in the future as <LSID>, and will be
viewable online at /metacat/metacat?action=read&cfg=esa&docid=esa.1 after publication. Thank you for your cooperation.

The Ecological Society of America

The <LSID> section and the "viewable online at .." path do not look right. Also currently if this is accepted their publication is accepted too.

Here is the error that show up on the current production server 1.8.0 when using the email link after logging in.
Failure
An error occurred. Please check the list of errors below:

• Next revision number couldn't be less than or equal 2
• Failed while updating.

Click the button below to return to the form and fill in the required fields. Do NOT use the back button on your browser. Submit the description again when you are finished.

Original Bugzilla ID was 2176