Actuellement ori-oai-workflow ne propose pas d'IHM permettant de changer le propriétaire / owner de la fiche.
Un administrateur peut le faire cependant manuellement en éditant directement la base de données.
Imaginons que l'on souhaite que toutes les fiches qui appartenaient à titi appartiennent maintenant à toto.
Voici la procédure à suivre :
- on stoppe le module ori-oai-workflow
- on se connecte à mysql et on fait la modification adéquate ainsi :
debian:/home/vincent# mysql -u root -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2261 Server version: 5.0.51a-24+lenny2-log (Debian) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> use ori-oai-workflow Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> update `ORI_WORKFLOW_ACL_ROLE` set `objRecipient` = 'toto' WHERE `objRecipient` = 'titi'; Query OK, 185 rows affected (0.02 sec) Rows matched: 185 Changed: 185 Warnings: 0
- On no'ublie pas de mette à jour l'index local utilisé en interne d'ori-oai-workflow :
debian:/opt/ori/src/ori-oai-workflow-spring$ ant local-reindexall Buildfile: build.xml prepare: compile-java: compile-web: compile: local-reindexall: [java] 1 WARN ehcache.CacheManager detectAndFixDiskStorePathConflict[271] - Creating a new instance of CacheManager using the diskStorePath "/tmp" which is already used by an existing CacheManager. [java] The source of the configuration was InputStream java.io.BufferedInputStream@32a325. [java] The diskStore path for this CacheManager will be set to /tmp/ehcache_auto_created_1255361499843. [java] To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance. BUILD SUCCESSFUL Total time: 36 seconds
- puis on relance le module ori-oai-workflow