User needs
Discussed at 2010 DC Conference by the NKOS Task Group
-
- A. In terms of ‘user needs’ in general, the Library Linked Data group summarized some based on the input of various communities:
Users needs:
Browse / explore / select
Retrieve / find
Identify
Access / obtain
Integrate / contextualize
Justify
Add information / annotate / comment
Source: http://www.w3.org/2005/Incubator/lld/wiki/Dimensions
These might also be useful for us to discuss the functional requirements because what we will specify as functions must satisfy users needs like these.
B. We may put the consideration into the lifecycle
B1. Properties to specify interactions of different KOS
Versioning
Modularization
Resources and Reuse
Crossreferences
Multirepresentation
B2. A list of the information life cycle activities in which
* the creators/authors, publishers, information systems managers,
service providers, and end users are all involved:
- 1) creation and modification;
- 2) publication;
- 3) acquisition, selection, storage, system and collection, building;
- 4) cataloging (metadata, identification/naming, registration), indexing, knowledge organization,
knowledge representation, and modeling;
- 5) integration, brokering, linking, syntactic and semantic interoperability engineering;
- 6) mediation (e.g., user interfaces, personalization, reference, recommendation, and transfer);
- 7) access, search, and discovery;
- 8) use, shared application/ collaboration, scholarly communication, annotation, evaluation, reuse, and work environments;
- 9) maintenance; and
- 10) archiving and preservation.
Source: Patel, M.; Koch, T.; Doerr, M.; Tsinaraki, C. Semantic interoperability in digital library systems. In DELOS Network of Excellence on Digital Libraries, European Union, Sixth Framework Programme. Deliverable D5.3.1, 2005; http://www.ukoln.ac.uk/ukoln/staff/t.koch/publ/SI-in-DLs.doc
B3. Information lifecycle
(This is about linked data, but the generalization will be helpful to us):
collect:
browse / explore / find / retrieve entities
* to select an entity appropriate to the user’s needs
- to acquire or obtain access to the entity
interpret / analyze / synthesize:
- to convert entities to another format
- to merge selected entities with local data
- to reason about selected entities
- to enrich existing entities with more data
- to identify an entity
- to contextualise the entities by connecting them with other entities
present / publish:
- to create or update entities
- to annotate, comment information
- to visualize entities and their relations
Justify, to document the authority data creator’s reason
- to make new entities accessible inside an information system
- to provide new data as LOD
Source: Dimensions -- Information lifecycle http://www.w3.org/2005/Incubator/lld/wiki/Dimensions