Requirements for a Registry Administration module

12731
Reporter: jcuadra
Type: Task
Summary: Requirements for a Registry Administration module
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-02-15 17:55:12.46
Updated: 2013-12-16 17:50:33.067
Resolved: 2013-12-11 17:44:33.109
        
Description: The following is a list of requirements for the Registry's Administration module. This lists integrates some JIRA issues as well as current functionality that should not be lost when creating the new admin module. This is an ongoing list, please add more requirements if needed.

===================
*Add an OVERWRITE checkbox at the top of the entity page in case the admin wants to block this entity from future updates through other SW tools (e.g. synchronizer)*

An admin should have the possibility to go into each entity page and click on an OVERWRITE checkbox. If this is set, then future updates coming from the synchronizer (or others) will not automatically update any properties. This checkbox has to be manually ticked, so if an admin comes in and edits any property, the checkbox will remain unactive (making the recent changes prone to overwriting in the next synchronizer execution)

Related to old issue: POR-218

===================
*When creating a new Organization, the relation with the endorsing Node should not be validated by default*

Instead offer a checkbox which the admin can click and automatically validate the endorsement, but the admin should have the option to leave the checkbox unchecked in case there are pending administrative issues before validating the endorsement

Related to old issue: POR-220

===================
*Offer a way to validate relationships between entities with a simple click*

If an organization has the "pendingEndorsement" flag active, the admin webapp should offer an easy way for the admin to validate the endorsement with a simple click. Basically, just keep the process simple.

Related to old issue: POR-222

===================
*When an endorsement has not been approved, offer a textfield where the admin can input the reason*

Once an organization is created, but the endorsement has not been approved due to administrative reasons, offer a textfield on the admin module so that the admin can provide the reason why the endorsement has not passed.

Related to old issue: REG-278

===================
*When creating a new entity (Organization, Dataset, etc), provide a visual hint to user about the required fields needed to be inputted*

A suggestion is to mark this fields with a {color:red}red color{color}  or a red {color:red}*{color}
See: http://blog.bucketsoft.com/2012/05/user-experience-3-required-fields-and.html

Related to old issue: POR-214

===================
*When editing an existing entity, if given the ability to edit existing relations (hosting organization, owning org, etc), the select boxes should iniatilly be disabled to avoid any unintented edits*

When an admin user wants to edit an entity, the EDIT screen should provide an ENABLE/DISABLE checkbox to avoid the user unintentionally changing the relationship of the entity. For example, for a EDIT DATASET page, the "OWNING ORGANIZATION" selectBox (or textfield, as required) should be disabled at first, with a checkbox just to the right of it. To edit this field, the admin should first click ENABLE (checkbox), the select "OWNING ORGANIZATION" becomes enabled again, and then make the changes.

This will also need to be in place for COUNTRIES as well.

Related to old issue: POR-219]]>
    

Author: kbraak@gbif.org
Created: 2013-12-11 17:44:33.264
Updated: 2013-12-11 17:44:33.264
        
All these requirements are fulfilled, in the new Registry Console.

Closing issue.