New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Story 6: As a data manager, I want an extra page for public data #33

Closed
DavidBlaa opened this Issue May 22, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@DavidBlaa
Member

DavidBlaa commented May 22, 2018

metadata info differs from internal data.

Having a public page that shows marked datasets to anonymous users.

  • the app would have two URLs for public datasets’ search and the current traditional search. The first one queries the search provider only for the datasets that are marked as public. (@DavidBlaa)
  • in the DDM's seed data generation, the public action must be added to publicly accessible actions in the security settings.
  • Dataset owners/managers decide which dataset is public. This flag is considered during indexing and search (@sventhiel). This is currently done through permission management, hence, after changing such permissions the corresponding dataset should be reindexed.
  • There would be a configurable landing page that is by default on the current search page, but admins can change it to the public search for anonymous users (@javadch).

@DavidBlaa DavidBlaa changed the title from USer Story 6: As a data manager, I want an extra page for public data to User Story 6: As a data manager, I want an extra page for public data May 22, 2018

@javadch

This comment has been minimized.

Show comment
Hide comment
@javadch

javadch Jun 20, 2018

Member

All the tasks are done.
Currently, when an admin sets/unsets one or more datasets to/from public, s/he should reindex the search.
I would suggest that @sventhiel integrates the reindexing feature into the function that controls the datasets' states so that the search index store remains in sync.

Member

javadch commented Jun 20, 2018

All the tasks are done.
Currently, when an admin sets/unsets one or more datasets to/from public, s/he should reindex the search.
I would suggest that @sventhiel integrates the reindexing feature into the function that controls the datasets' states so that the search index store remains in sync.

@javadch javadch closed this Jun 20, 2018

javadch added a commit that referenced this issue Jun 20, 2018

javadch added a commit that referenced this issue Jun 20, 2018

DavidBlaa added a commit that referenced this issue Jun 26, 2018

DavidBlaa added a commit that referenced this issue Jun 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment