editorial workflow

Dear Helma

have been talking with Sergio Carmona about the update process of the website. Currently, update is completely live, which is convenient, but could also be dangerous, for obvious reasons.

It would be desirable to allow multiple people to work on the site, particularly for translation purposes and to have something like the following controls, to prevent us from publishing dumb mistakes - they do happen!

  • define groups of users, e.g. openehr.cl group, openehr.jp group
  • each group can have multiple users with modifying capability, including to only some parts of the website, e.g. /chile/ variant (however it is called)
  • changes are not published instantly on save, but instead a nominated person or email address receives a message to indicate what has changed, and to review and ok it.
    Note that I am not advocating a ‘heavy’ reviewing process, but rather a minimum editorial control so that any of us don’t break somehting major on the site due to an unintended error. Equally, we probably should be realistic and expect that logins to the site may be stolen one day and that a malicious users might deface the site, so for this reason, an authorisation step should be introduced to allow a check to be made before publishing; where errors are found, the proposed change is blocked.

So, the question is: can Daisy support this mode of working? Or somthing equivalent?

thanks,

  • thomas
(attachments)

OceanCsmall.png

Dear all,

just a quick reply to explain my recent absence. Currently I'm out of an
internet connection at home which is where I do the work on the openEHR
site. Defining the layout of the Chilean site is something I'm working
on offline and I'll give the question below a test too.
With the deadline of my PhD approaching fast and the upcoming holidays I
need all the available time and focus at work to get this beast conquered.
I'm told that my internet connection would be activated around 14
December and I'm currently trying to move that date earlier. So until
then, please be patient.

To give some answers: yes, Daisy can handle such things. I'm currently
not sure if rights can be defined on variant level, but definitely on
collection level. Rights are granted in a role based system and users
can have multiple roles.

Thank you.

Bye, Helma

Thomas Beale said the following on 21/11/07 19:15: