EPrints User Group 2015-01-13 - Revision history

J.beaman@leeds.ac.uk at 17:48, 12 January 2015

2015-01-12T17:48:53Z

← Older revision		Revision as of 17:48, 12 January 2015
Line 1:		Line 1:
			{{AccessControl}}
	John Salter and John Beaman, University of Leeds		John Salter and John Beaman, University of Leeds

2015-01-09T14:59:12Z

ACL Objects

← Older revision		Revision as of 14:59, 9 January 2015
Line 45:		Line 45:
	**The ACL Roles are combined within an ACL Group by being 'OR'ed or 'AND'ed together		**The ACL Roles are combined within an ACL Group by being 'OR'ed or 'AND'ed together
	**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)		**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)
	**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed ~~togther~~		**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed together


	===Request vs User===		===Request vs User===

2015-01-09T14:07:57Z

← Older revision		Revision as of 14:07, 9 January 2015
Line 5:		Line 5:
	* We've spent some time trying to write an Access Control system for EPrints. ''It's been a horror.''		* We've spent some time trying to write an Access Control system for EPrints. ''It's been a horror.''
	* One of our use-cases is for Research Data, but it could be used on other repository types.		* One of our use-cases is for Research Data, but it could be used on other repository types.


	==Out of the box User Access Control==		==Out of the box User Access Control==
Line 12:		Line 13:
	** staffonly (Repository editors/admins)		** staffonly (Repository editors/admins)
	* This doesn't cover the requirements for some repositories...		* This doesn't cover the requirements for some repositories...


	==Requirements==		==Requirements==

2015-01-09T14:07:27Z

← Older revision		Revision as of 14:07, 9 January 2015
Line 22:		Line 22:

	==EPACL: EPrints Access Control Layer==		==EPACL: EPrints Access Control Layer==


	===Modular Design===		===Modular Design===
Line 28:		Line 29:
	*ACL Authority modules governing different methods of Authentication (see later) can be developed separately		*ACL Authority modules governing different methods of Authentication (see later) can be developed separately
	*These modules can simply be 'dropped in' to the existing framework as required		*These modules can simply be 'dropped in' to the existing framework as required


	===ACL Objects===		===ACL Objects===
Line 42:		Line 44:
	**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)		**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)
	**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed togther		**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed togther


	===Request vs User===		===Request vs User===

2015-01-09T10:26:18Z

Modular Design

← Older revision		Revision as of 10:26, 9 January 2015
Line 26:		Line 26:
	*Doesn't overwrite any existing 'security' specified on documents.		*Doesn't overwrite any existing 'security' specified on documents.
	*Will be available as a standard EPrints Plugin (EPM package) via the EPrints Bazaar		*Will be available as a standard EPrints Plugin (EPM package) via the EPrints Bazaar
	*ACL Authority modules governing different methods of ~~Authorisation and~~ Authentication (see later) can be developed separately		*ACL Authority modules governing different methods of Authentication (see later) can be developed separately
	*These modules can simply be 'dropped in' to the existing framework as required		*These modules can simply be 'dropped in' to the existing framework as required


	===ACL Objects===		===ACL Objects===

2015-01-09T10:25:27Z

ACL Objects

← Older revision		Revision as of 10:25, 9 January 2015
Line 32:		Line 32:
	===ACL Objects===		===ACL Objects===
	*ACL Authority		*ACL Authority
	**Corresponds to a method of ~~authorisation~~ (e.g. Shibboleth, LDAP etc.)		**Corresponds to a method of authentication (e.g. Shibboleth, LDAP etc.)

	*ACL Role		*ACL Role
Line 43:		Line 43:
	**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)		**One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents)
	**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed togther		**The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed togther


	===Request vs User===		===Request vs User===

2015-01-08T17:40:08Z

← Older revision		Revision as of 17:40, 8 January 2015
Line 69:		Line 69:
	*Individual documents may have their own DOI, so ideally need their own 'landing page'		*Individual documents may have their own DOI, so ideally need their own 'landing page'
	*Document landing pages should contain at least the mandatory metadata fields if linked from a DOI		*Document landing pages should contain at least the mandatory metadata fields if linked from a DOI



	===The horrors (and the solutions)===		===The horrors (and the solutions)===

2015-01-08T17:39:37Z

Document-level landing pages

← Older revision		Revision as of 17:39, 8 January 2015
Line 66:		Line 66:

	===Document-level landing pages===		===Document-level landing pages===
	*~~Born~~ out of DOI requirements		*Partly born out of DOI requirements
	*Individual documents may have their own DOI, so ideally need their own 'landing page'		*Individual documents may have their own DOI, so ideally need their own 'landing page'
	*Document landing pages should contain at least the mandatory metadata fields if linked from a DOI		*Document landing pages should contain at least the mandatory metadata fields if linked from a DOI


	===The horrors (and the solutions)===		===The horrors (and the solutions)===

2015-01-08T17:36:00Z

← Older revision		Revision as of 17:36, 8 January 2015
Line 79:		Line 79:
	*EPrints doesn't use 'sessions' in the same way as most other web software. Sessions are only created when a user logs in (we think user accounts need to be automatically created - is this right? It would be useful for tracking re-use)		*EPrints doesn't use 'sessions' in the same way as most other web software. Sessions are only created when a user logs in (we think user accounts need to be automatically created - is this right? It would be useful for tracking re-use)
	EPrints documentation is ahem* offering room for improvement /ahem...		EPrints documentation is ahem* offering room for improvement /ahem...


	==Homeless thoughts==		==Homeless thoughts==

2015-01-08T17:35:03Z

← Older revision		Revision as of 17:35, 8 January 2015
Line 19:		Line 19:
	** Location / IP address (e.g. on-campus)		** Location / IP address (e.g. on-campus)
	* Simple interface to assign restrictions		* Simple interface to assign restrictions


	==EPACL: EPrints Access Control Layer==		==EPACL: EPrints Access Control Layer==

	===Modular Design===		===Modular Design===
	*Doesn't overwrite any existing 'security' specified on documents.		*Doesn't overwrite any existing 'security' specified on documents.
Line 26:		Line 28:
	*ACL Authority modules governing different methods of Authorisation and Authentication (see later) can be developed separately		*ACL Authority modules governing different methods of Authorisation and Authentication (see later) can be developed separately
	*These modules can simply be 'dropped in' to the existing framework as required		*These modules can simply be 'dropped in' to the existing framework as required


	===ACL Objects===		===ACL Objects===