Changes between Initial Version and Version 1 of workflow_integration


Ignore:
Timestamp:
Jan 15, 2008, 5:14:41 AM (16 years ago)
Author:
fbachraty
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • workflow_integration

    v1 v1  
     1= Proposal number : Simple Workflow integration =
     2
     3|| '''Date''' || 2008/01/15 ||
     4|| '''Contact(s)''' || Fabien fbachraty. ||
     5|| '''Last edited''' || [[Timestamp]] ||
     6|| '''Status''' || draft ||
     7|| '''Assigned to release''' || To be determined ||
     8|| '''Resources''' || I have already implement the functionality for my own project ||
     9
     10== Overview ==
     11
     12The purpose of this proposal is to permit the administrators and reviewer to know who create the metadatas, and who do the last update for the geonetwork local node. ( For controlling publication content as example ).
     13
     14So a simple Workflow functionality, witch just save the user id of the metadata owner and metadata updater, will permit to display for the administrators and reviewer, complementary and very interesting information about the metadata like :
     15
     16                - Creation Date : User Groups - User <with email link>
     17                - Update Date  : User Groups - User <with email link>
     18...
     19
     20Create and update date can be displayed for all user.
     21
     22=== Proposal Type ===
     23 * '''Type''': GUI Change, Core Change
     24 * '''App''': GeoNetwork
     25 * '''Module''': Kernel, Data Manager,XmlSerializer,EditUtils,Edit
     26
     27=== Links ===
     28 * '''Documents''':
     29 * '''Email discussions''': http://www.nabble.com/forum/ViewPost.jtp?post=12975916&framed=y&skin=18419
     30 * '''Other wiki discussions''':
     31
     32=== Voting History ===
     33 * Not yet proposed for voting.
     34
     35----
     36
     37== Motivations ==
     38Sometime the publisher is also the legal responsible of the content publish so it is important to know who create and update the metadata.
     39It is also important to know when the last update has been done.
     40
     41== Proposal ==
     42An example of implementation result can be found here :
     43http://www.nabble.com/forum/ViewPost.jtp?post=14834966&framed=y&skin=18419
     44
     45=== Backwards Compatibility Issues ===
     46It's needed the add a field in the database (on the metadata table) so if it integrate the core the gast tool and import export tool may manage it.
     47
     48I use postgres function Coalesce on my SQL code implementation that can be incompatible with other database like oracle as example.
     49
     50In all case I start with java so it is better to review my code source before to integrate it.
     51
     52== Risks ==
     53
     54== Participants ==
     55 * Fabien Bachraty