This is an automated notification sent by LCG Savannah.
It relates to:
task #6995, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #6995:
==============================================================================
Update of task #6995 (project cdsware):
Status: None => Done
Percent Complete: 0% => 100%
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Action bibedit now takes optional arguments.
Demo site configuration is enriched with new roles:
1. curator - can run bibedit on all records: Dorian
2. photocurator - can run bibedit on records in Pictures collection: Juliet
3. thesescurator - can run bibedit on records in Theses collection: Romeo
4. bookcurator - can run bibedit on records in Books collection: Jekyll
New testcases:
test_bibedit_basic_record_locking
test_bibedit_reedit_warning (fixed bug to make this one work)
test_bibedit_access_none
test_bibedit_access_collection
test_bibedit_access_all
==============================================================================
OVERVIEW of task #6995:
==============================================================================
URL:
<http://savannah.cern.ch/task/?6995>
Summary: bibedit demo users setup
Project: CDS Invenio
Submitted by: simko
Submitted on: 2008-06-03 16:28
Should Start On: 2008-06-03 00:00
Should be Finished on: 2008-06-03 00:00
Category: BibEdit
Priority: 7 - High
Status: Done
Privacy: Public
Percent Complete: 100%
Assigned to: lraae
Open/Closed: Closed
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
The demo site configuration should be enriched so that we can easily test
locking of records. E.g. Romeo and Juliet should both have record editing
rights, but Benvolio should not. (Technically, see democfgdata.sql and
DEF_DEMO_USER_ROLES in access_engine_config.py.)
When the test users for bibedit are ready, the locking of records should get
tested by writing a few Selenium web test suite cases.
Some examples: (1) When Romeo opens a record for editing, then Juliet should
be denied access to editing this record. (2) When Romeo would like to reopen
a record he already edits, he should get a warning. (3) Benvolio should always
be denied access to edit records. (4) We can have a user that can edit only
records belonging to a certain collection, say Pictures, but not others, say
Poems. (5) Since Theses is already a restricted demo collection, we can
expect that an "ordinary" cataloguer should not have rights to edit theses
records, only specially enabled cataloguers. Etc.
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: 2008-06-23 17:11 By: Lars Christian Raae <lraae>
Action bibedit now takes optional arguments.
Demo site configuration is enriched with new roles:
1. curator - can run bibedit on all records: Dorian
2. photocurator - can run bibedit on records in Pictures collection: Juliet
3. thesescurator - can run bibedit on records in Theses collection: Romeo
4. bookcurator - can run bibedit on records in Books collection: Jekyll
New testcases:
test_bibedit_basic_record_locking
test_bibedit_reedit_warning (fixed bug to make this one work)
test_bibedit_access_none
test_bibedit_access_collection
test_bibedit_access_all
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
3871 | -COM-
1576 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?6995>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
