-
Notifications
You must be signed in to change notification settings - Fork 15
Document Sets
Searching variables/datasets/studies/networks is the first step in the data exploration. The second step is the exploitation of the found documents: saving sets of variables, exporting data dictionaries, composing variable sets, getting some taxonomy coverage statistics, binding a variable set to a data access request, searching entities matching variables from a variable set etc.
Adding documents to a cart and saving them in sets are features available to anyone, i.e. authentication is not required.
See also GDC Save Sets Specification As An Example.
Make search in the web data portal more useful.
Describe simply who is doing what and how to obtain the result.
| # | Who | What | How | Result |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| ... |
Server and (js) client.
A document (variables etc.) set is a set of documents that is:
- explicitly described by an enumerated list of variable identifiers OR described by a composition of several sets
- associated to a user
- uniquely identified
- described by a human readable name
Despite it would be very convenient to store the document set on client side, due to the limit of the browser database the documents set must always be persisted on server side (even for anonymous users) and the client will only handle the sets meta information (name, number of documents etc.). Document set operations are also performed on server side: union, intersection, complement, export etc.
How can the feature be tested or demonstrated. It is important to describe this in fairly great details so anyone can perform the demo or test.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.