Skip to content
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

installation: decide on restriction policy #3677

Open
tiborsimko opened this issue Jul 19, 2016 · 7 comments
Open

installation: decide on restriction policy #3677

tiborsimko opened this issue Jul 19, 2016 · 7 comments

Comments

@tiborsimko
Copy link
Member

Let's try to decide what would be the recommended restriction system fitting most service use cases, and let's plug it into Invenio 3 demo site records.

  • using collections?
  • using ACLs in records?

See also inveniosoftware/invenio-access#70

@kaplun
Copy link
Member

kaplun commented Jul 19, 2016

👍 for restricted collections.

@lnielsen
Copy link
Member

+1 for ACL in records. Restricted collections can be built on top of this.

@kaplun
Copy link
Member

kaplun commented Jul 20, 2016

+1 for ACL in records. Restricted collections can be built on top of this.

👍 also for ACLs then 😄

@egabancho
Copy link
Member

+1 for ACL in records

@aw-bib
Copy link
Contributor

aw-bib commented Jul 21, 2016

While this is for records, one should probably think about handling for files attached to records as well.

@egabancho
Copy link
Member

@aw-bib #3680 😉

@tiborsimko
Copy link
Member Author

It may be better to discuss in inveniosoftware/invenio-access#70 where @egabancho nicely summarised all the pros and cons...

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

No branches or pull requests

5 participants