Metacat

Tonight, I modified the moderators number (reduced from 2 to 1). But new package still has the same problem. So the previous guess is wrong. I will set local test in my machine.

Here is another problem area. For some unknown reason I had one success with using the Moderator account to give access to edit a data package. To do this I went to the View Submissions area clicked on a data set link and wrote a little note about revising the dp, then clicked on the revise button. Then I logged in as the user owner of the dp and WAS ABLE TO EDIT using the edit button. I think this is how we originally set it up. Once the dp is submitted by the owner it can only be edited with the ESA form after the moderator asks for revisions.

I tried to repeat this method but I got the following error after clicking on the revise button in the window where the moderator views the individual dps.

"Failure in requesting revision of docid: esa.42.1 ( Failed while updating the document with additional Metadata.) 3 data set(s) found for moderation"

The dps that had the revise button clicked after adding a little note (and got the failure response)are no longer viewable. I remember this happening before but I thought it was fixed. I could not find a bug for it.

(Note the revise button to the right of the list of dps available to view does not apear to respond. What happens when this gets clicked?????)  The only way to look at the individual dps is by clicking on the dp link. I think there is a problem with having the buttons on the right next to the dp list. It is confusing, because one does not know if they are working are not.

I think we need to iron out any additional needed dialog boxes. One for when the owner clicks on the edit feature but does not have rights if the moderator hasn't reviewed it. One for when the moderator writes a comment and clicks on the revise button. (Something like revision request sent).

The reason why user couldn't edit the submitted document is in the cgi script, there is a rule that the access allow rules couldn't be less or greater than 3. Otherwise, user will get the error. I don't see any reason we need that (Probably I missed something). However I takes out the rule and register form seems working fine to me. I will ask callie to do more extensive testing on my test machine. If everything seems good to her. I will check in the changes I made.

Original Bugzilla ID was 2841