Group items tagged

Overview of what are non-functional requirements

Interesting as inspiration for D2.4 although they seem to take a different approach. Listing requirements per content provider with the objective of making each content provider into a EDM resource. You could say they have developped tailored ECK to be fully implemented into the local ICT infrastructure of content providers.

Although a very different context of use this deliverable has a lot to learn for EU-Inside

Although the context of use is different, this document comes closes to what we have to deliver as D2.2. so far.

The IPR Wizard can be used by partners (affiliated or contractors) only. Those partners have in charge one groups/channel at which their content is associated with, any institution and/or company may get affiliated with ECLAP. The groups coordinator may ask to have among its affiliated people one or more IPR Managers. To this end, an email has to be sent to info@eclap.eu. The IPR Managers may use the IPR Wizard to set up permissions and restrictions about the usage of the published content on ECLAP portal and related mobile devices according to the ECLAP terms of use. (...)

IPR whizard from the ECLAP project

A good example for D2.4? Although in the document it says: we must stress that this document is neither a Functional Requirements nor a Technical Specifications document. It's unclear to me if such documents have been produced in the HOPE project and if they are accessible to us.

The issue of Persistent Identifiers in ATHENA

The annex lists user requirements but they are very basic descriptions in which the end users on the web are always actors. Less relevent as an example for D2.4 I guess.

helps institutions to choose the appropriate license for their content.