Support public visibility of development ('private') components

[Twan Goosen]

Note: this concerns a partial implementation of the feature described by #142

Description: There should be an option to mark private (either group or individual user) components and profiles as publicly visible. The owner(s) of a component decide on this state. Components marked as such should be visible in both the list of public components/profiles (but only if enabled by the viewing user) and in the user's/group's private list.

1. Add a property representing 'public visibility' to components and profiles (i.e. change model + database schema).
   Note: The 'public' property should remain untouched (will be partly replaced by a 'status' property in CMDI 1.2, see #142).

2. Support this in the REST backend

/registry/components?userSpace={userSpace}&showDraft={showDraft}

pseudo-sql (conceptual, does not have to be implemented in one query):

select * from components 
   where 
      "isPublic" != userSpace AND (!userSpace OR "owner" = uid)
      OR 
        !userSpace AND showDraft AND "publiclyVisible" = TRUE

defaults: {userSpace}=false; {showDraft}=false (has no effect when userSpace=true)

2. Add a button to toggle the 'publiclyVisible' property of a component (probably next to move to group)

3. In the UI, add a checkbox to the view of public components or profiles that binds to the 'showDraft' option, allowing the user to filter out (default behaviour) draft components

4. Add a clear indication (e.g. DRAFT) of this status in the components/profiles table!

[Twan Goosen]

​https://github.com/clarin-eric/component-registry-rest/issues/13

[Twan Goosen]

Ticket retargeted after milestone deleted