From: Francois P. <fx....@gm...> - 2012-09-27 07:21:20
|
Hi, I've been testing the workflow proposal on one of the clustering node and have some more comments on the workflow: * if you create a record, go to privilege and publish to internet, the record is not yet published - because it's not approved - so maybe privileges should not be accessible for a workspace copy ? or a warning should be displayed in the privilege. * when changing status to approved, it looks like the metadata is published to all automatically - the metadata should keep its privileges, even if it's approved it could be a non public (for internet) record. Any options to configure that ? "approved" should not mean "publish to internet" I think. * it could be nice to provide an option to disable/bypass the feature where the save action behave as currently (so maybe copying the workspace copy to the metadata when saving) and all the new options in menu are hidden - this keep the user interface not too complex with less options which may be not of interest for all. With the workflow, the number of clicks to make a change is doubled and we probably have some user who would like to make changes with less click ... with inline text editing feature for example. * about menu, at some point we should maybe group actions by category because the list of choice is sometime very long and user may be lost. So grouping editing/viewing actions together at least. Cheers. Francois 2012/9/24 Francois Prunayre <fx....@gm...>: > +1 for me. Nice improvements. > > Francois > > 2012/9/23 <Sim...@cs...>: > > >> Just one extra note: Could be an issue with Z3950 server ports - each >> servlet will try and start a Z server on the same port: resulting behaviour >> would depend on the config of servlets and machines (this is GN's Z server >> capability - this shouldn't affect GN's ability to harvest/search other >> Z3950 servers ie. when it is used as a Z client). > >> Who depends on GN as a Z server? I know that the Australian Spatial Data >> Directory as currently config'd does use GN as a Z server, but it could use >> a different protocol/interface to talk to GeoNetwork sites especially as >> JZKit in GN doesn't implement some of the hacks for getting all records from >> a Z server. Could be also that those who want GN as a Z server could switch >> to using the SRU/SRW http based Z capability (this shouldn't be affected by >> this proposal)? >> >> Cheers, >> Simon >> ________________________________________ >> From: Sim...@cs... [Sim...@cs...] >> Sent: Saturday, 22 September 2012 5:07 PM >> To: tro...@gm...; geo...@li... >> Subject: [ExternalEmail] Re: [GeoNetwork-devel] CFV: Clustering and >> Improvements to workflow >> >> Heikki & Jose & Steven, >> >> +1 from me. >> >> Reviewed the proposals and have some brief notes/comments: >> >> 1. Load Balancing >> >> - Really keen to see this proposal get up - helps us make much better use >> of machines with lots of processors etc >> - Had some concerns about UUID handling and what was being proposed but I >> can see from using the test sites that you have not mixed the UUID for the >> db with the UUID/identifiers for the metadata - so looks ok! >> >> 2. Workflow >> >> - Seems that any changes made to the metadata would not be recorded in the >> versioning/subversion repo until the metadata leaves the workspace table - >> this could be desirable as it avoids cluttering the versioning/subversion >> repo with lots of little changes. >> - We could use the graphical diff comparison interface with a selector to >> compare different versions of a metadata record in versioning/subversion >> repo maybe in a future proposal >> - I like the stricter controls on what can happen with state changes, the >> workspace concept to protect published metadata from changes etc and the >> better locking - nice >> >> Cheers, >> Simon >> >> ________________________________________ >> From: heikki [tro...@gm...] >> Sent: Saturday, 22 September 2012 12:25 AM >> To: Devel geo...@li... >> Subject: [GeoNetwork-devel] CFV: Clustering and Improvements to workflow >> >> dear PSC members, >> >> please vote on these two proposals: >> >> http://trac.osgeo.org/geonetwork/wiki/LoadBalanceable >> >> This proposal makes it possible to cluster GeoNetwork, allowing for >> horizontal scaling. >> >> http://trac.osgeo.org/geonetwork/wiki/ImprovedWorkflow >> >> This proposal makes improvements to GeoNetwork's metadata lifecycle, the >> workflow, it repairs the broken pessimistic locking in GeoNetwork and >> itroduces a graphical Metadata Difference Viewer. >> >> >> We're asking for a vote on both proposals together because the Clustering >> proposal needs the Improvements to Workflow to function correctly. >> >> >> You can see the code in a GitHub branch here: >> https://github.com/heikkidoeleman/core-geonetwork/tree/clusteringworkflow. >> This code applies the changes of the two proposals to the version in the >> GeoNetwork master branch of a few days ago. >> >> >> A very quick vote would be much appreciated. >> >> Kind regards >> Heikki Doeleman & Jose García >> >> >> >> >> >> ------------------------------------------------------------------------------ >> How fast is your code? >> 3 out of 4 devs don\\\'t know how their code performs in production. >> Find out how slow your code is with AppDynamics Lite. >> http://ad.doubleclick.net/clk;262219672;13503038;z? >> http://info.appdynamics.com/FreeJavaPerformanceDownload.html >> _______________________________________________ >> GeoNetwork-devel mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel >> GeoNetwork OpenSource is maintained at >> http://sourceforge.net/projects/geonetwork >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://ad.doubleclick.net/clk;258768047;13503038;j? >> http://info.appdynamics.com/FreeJavaPerformanceDownload.html >> _______________________________________________ >> GeoNetwork-devel mailing list >> Geo...@li... >> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel >> GeoNetwork OpenSource is maintained at >> http://sourceforge.net/projects/geonetwork |