Hi Antoine,
does the requirements tree appear now as you wanted it to appear?
Now, if you edit requirements, the selection of associated requirements classes is displayed at the end of the editor.
Does this satisfy your requirement?
When you edit requirements you see now a select list for associations with use cases and not a list of check boxes.
You can select multiple use cases in order to relate requirements to use cases.
The same appears now for the requirements classification.
Related to your comment during the discussion.
If you have a requirement in mind and you are not sure if it is already contained in the requirements db, just create an new requirement.
I can look if there is already a requirement in the db with the same semantics in order to delete duplicates.
Cheers,
Thomas
--
Thomas Bosch, M.Sc. (TUM)
PhD student
GESIS - Leibniz Institute for the Social Sciences
Social Science Metadata Standards
Visitors Address: B2,1, D-68159 Mannheim
Postal Address: P.O.Box 12 21 55, D-68072 Mannheim
Tel: + 49 (0) 621 / 1246-271
Fax: + 49 (0) 621 / 1246-100
Web: http://www.gesis.org
Website: http://boschthomas.blogspot.com/
GitHub: https://github.com/boschthomas/PhD
-----Ursprüngliche Nachricht-----
Von: DCMI Architecture Forum [mailto:[log in to unmask]] Im Auftrag von Antoine Isaac
Gesendet: Dienstag, 8. Juli 2014 18:02
An: [log in to unmask]
Betreff: Feedback DB validation requirements
Dear all,
Following the discussion in today's call on
http://purl.org/net/rdf-validation
I had extra comments:
- the left menu with the requirement 'tree' is hard to follow. Is there a way in Drupal to make the branches (un)fold upon a click, not a mouse-over?
- the number of classes for requirements really high. As such in the edition form, it's really standing between the editor and the most important stuff (the description of the requirement). Is it possible to put the requirement classification part at the end of the edition template? And to remove some of the tickboxes?
Best,
Antoine
|