Hi Thomas,
This is great!
As long as the DC category on the left doesn't give access to a full-blown facet/hierarchy (e.g. having "DC constraint expressivity" below it) I think you can safely remove it, it is quite redundant with what you've added on the tab.
Cheers,
Antoine
PS: well done on the new [RDF AP] subject policy!
On 7/30/14 7:33 AM, Bosch, Thomas wrote:
> Hi,
>
> I added new functionality to the requirements database:
>
> -new field for case studies ‚case study classes‘. You can assign the class ‘Dublin Core Case Study’ to a case study (to demonstrate I only assigned case study 1 and 3 to the class of DC case studies so far)
>
> -new view on DC case studies: http://lelystad.informatik.uni-mannheim.de/rdf-validation/?q=case-studies/dc-case-studies
>
> -new view on DC use cases: http://lelystad.informatik.uni-mannheim.de/rdf-validation/?q=use-cases/dc-use-cases
>
> -new view on DC requirements: http://lelystad.informatik.uni-mannheim.de/rdf-validation/?q=requirements/dc-requirements
>
> èthese views are derived from DC case studies
>
> Then we do not need the requirements class ‘DC requirements’ anymore, as assignments of requirements to requirements classes directly are too error-prone.
>
> As a consequence, the requirements class ‘Dublin Core Requirements’ won’t be needed anymore and won’t be visible in the left sidebar.
>
> If there is consensus about this, I delete this requirements class from the requirements class taxonomy.
>
> Does this fit your intended functionality?
>
> Best,
>
> 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 <http://www.gesis.org/>
>
> Website: http://boschthomas.blogspot.com/
>
> GitHub: _https://github.com/boschthomas/PhD_
>
|