EPrints4 Status - Revision history

Th.lauke@arcor.de: link added

2024-02-19T13:27:35Z

link added

← Older revision		Revision as of 13:27, 19 February 2024
Line 10:		Line 10:
	==Database==		==Database==

	* Preferred MySQL engine is now InnoDB (over MyISAM)		* Preferred MySQL engine is now [[Converting_MyISAM_tables_to_InnoDB\|InnoDB]] (over MyISAM)
	* Added support for transactions with InnoDB. Partially written data/data-objects may be roll-backed (they are if an error occurs)		* Added support for transactions with InnoDB. Partially written data/data-objects may be roll-backed (they are if an error occurs)
	* Connects on demand		* Connects on demand

Kgoetz: Change category Developer to Contribute

2018-09-11T23:53:22Z

Change category Developer to Contribute

← Older revision		Revision as of 23:53, 11 September 2018
Line 1:		Line 1:
	[[Category:Eprints4]]		[[Category:Eprints4]]
	[[Category:~~Developer~~]]		[[Category:Contribute]]

	Packages that are considered "CORE": [[EPrints4_CORE]]		Packages that are considered "CORE": [[EPrints4_CORE]]

Kgoetz: adding categories

2018-08-30T06:38:35Z

adding categories

← Older revision		Revision as of 06:38, 30 August 2018
Line 1:		Line 1:
			[[Category:Eprints4]]
			[[Category:Developer]]

	Packages that are considered "CORE": [[EPrints4_CORE]]		Packages that are considered "CORE": [[EPrints4_CORE]]

Sf03r@ecs.soton.ac.uk at 14:19, 23 May 2014

2014-05-23T14:19:31Z

← Older revision		Revision as of 14:19, 23 May 2014
Line 1:		Line 1:

			Packages that are considered "CORE": [[EPrints4_CORE]]

	Things which have been tested / implemented:		Things which have been tested / implemented:

Sf03r@ecs.soton.ac.uk at 14:07, 25 March 2014

2014-03-25T14:07:33Z

← Older revision		Revision as of 14:07, 25 March 2014
Line 76:		Line 76:
	* contextual debugging: allows to enable/disable only specific themes e.g. "db", "security" etc. and only write status messages to the logs for the enabled themes		* contextual debugging: allows to enable/disable only specific themes e.g. "db", "security" etc. and only write status messages to the logs for the enabled themes
	* much, much more!		* much, much more!

			=UI=

			* Template using Bootstrap
			* Data-binding with JS Framework AngularJS
			* Dynamical pages served through light-weight Screen plug-ins (only handles the security aspect - who can see this page - and the "page's actions" via AJAX)

Sf03r@ecs.soton.ac.uk: /* Database */

2014-03-25T13:39:56Z

Database

← Older revision		Revision as of 13:39, 25 March 2014
Line 7:		Line 7:
	* Preferred MySQL engine is now InnoDB (over MyISAM)		* Preferred MySQL engine is now InnoDB (over MyISAM)
	* Added support for transactions with InnoDB. Partially written data/data-objects may be roll-backed (they are if an error occurs)		* Added support for transactions with InnoDB. Partially written data/data-objects may be roll-backed (they are if an error occurs)
			* Connects on demand

	==Request handlers/routers==		==Request handlers/routers==

Sf03r@ecs.soton.ac.uk: /* Nisc */

2014-03-24T17:19:35Z

Nisc

← Older revision		Revision as of 17:19, 24 March 2014
Line 70:		Line 70:
	** contexts: allows to add custom security contexts (eg. 'owner', 'editor', 'co-author')		** contexts: allows to add custom security contexts (eg. 'owner', 'editor', 'co-author')

	==~~Nisc~~==		==Misc==

	* memcached: use of server-wide "memcached" service to memory cache data objects		* memcached: use of server-wide "memcached" service to memory cache data objects
	* contextual debugging: allows to enable/disable only specific themes e.g. "db", "security" etc. and only write status messages to the logs for the enabled themes		* contextual debugging: allows to enable/disable only specific themes e.g. "db", "security" etc. and only write status messages to the logs for the enabled themes
	* much, much more!		* much, much more!

Sf03r@ecs.soton.ac.uk: /* Database */

2014-03-24T17:18:33Z

Database

← Older revision		Revision as of 17:18, 24 March 2014
Line 6:		Line 6:

	* Preferred MySQL engine is now InnoDB (over MyISAM)		* Preferred MySQL engine is now InnoDB (over MyISAM)
	* Added support for transactions with InnoDB. Partially ~~committed~~ data/data-objects may be roll-backed (they are if an error occurs)		* Added support for transactions with InnoDB. Partially written data/data-objects may be roll-backed (they are if an error occurs)

	==Request handlers/routers==		==Request handlers/routers==

Sf03r@ecs.soton.ac.uk: Created page with 'Things which have been tested / implemented: =CORE= ==Database== * Preferred MySQL engine is now InnoDB (over MyISAM) * Added support for transactions with InnoDB. Partially c…'

2014-03-24T17:18:10Z

Created page with 'Things which have been tested / implemented: =CORE= ==Database== * Preferred MySQL engine is now InnoDB (over MyISAM) * Added support for transactions with InnoDB. Partially c…'

New page

Things which have been tested / implemented:

=CORE=

==Database==

* Preferred MySQL engine is now InnoDB (over MyISAM)
* Added support for transactions with InnoDB. Partially committed data/data-objects may be roll-backed (they are if an error occurs)

==Request handlers/routers==

* Every request is now routed via a trigger call (to find out which controller will respond)
* Apache::Rewrite has been refactored to Apache::Handler and is now super-lightweight
* Support for CGI scripts has been removed

==Controllers==

* CRUD
* Storage (delivery of files/thumbnails)
* Counter (like /cgi/counter)
* Ping (for fun, just replies 'pong')
* UI (for, potentially, Screen plug-ins)
* Static pages (XHTML, XPAGES etc that need compilation to HTML or any other static file (js, css...)

==Security==

* Based around actions (e.g. edit, view, search, ...) and optional contexts ('owner', etc.)
* Low-level implementation to avoid objects to leak from one dataset ('inbox') to another ('archive')
* ACL dataset (should maybe be called 'privs') to store extra privs against a user
* finer-grain permission (down to a single dataobj)

==Auth==

* Rewritten auth mechanisms
* Done similarly to Controllers, via a trigger
* When a user is auth'ed a user-session is created (cf. login ticket)
* When a request comes, EPrints attempts to load a user-session - cf. above
* Supports AuthBasic when no UI is available
* Cookies are managed transparently behind the "user-session"

==Storage==

* Added support for generic files. It is now possible to store any file against any object.
* Added support for "thumbnails" (as a separate dataset)

==CRUD==

* CRUD extended to support more methods/URI etc
* Sword2 hacks temporarily removed from CRUD
* Doesn't require its own auth code anymore
* CrudClient available to perform remote operation on a repository (via CrudDataSet, CrudDataObj, CrudList etc) - the API is very similar to the standard CLI syntax to create/edit/etc objects/lists of objects.
* Support for ETag and If-None-Match
* Support for PATCH method
* Support for generic file upload
* Minimal support for searching a dataset (e.g. GET /data/user/) - though will probably have a separate /search/... interface to allow user queries (Xapian and the likes)
* Entry poing /id/... moved to /data/...

==Dataset definition==

* The following properties are now core (meaning that EPrints will automatically add appropriate fields, set/update/remove data when such or such properties are enabled):
** flow: replaces eprint_status and the likes. Allows to specify a flow of states and transitions
** revision: adds a revision number, incremented each time the data obj is modified
** acl (TO RENAME): allows ACL checks on the dataset (should always be ON)
** read-only: make the dataset read-only, no modifications are allowed via the API (whether HTTP, CLI ...)
** web-read-only (TOFIX): make the dataset read-only ONLY for HTTP requests - CLI scripts can still change data
** history (TODO): keeps an historic of changes
** lastmod: keeps a timestamp of when the data-obj was last modified
** datestamp: keeps the date of creation of a data-obj
** loghandler (TODO): keeps download stats for that dataset
** contexts: allows to add custom security contexts (eg. 'owner', 'editor', 'co-author')

==Nisc==

* memcached: use of server-wide "memcached" service to memory cache data objects
* contextual debugging: allows to enable/disable only specific themes e.g. "db", "security" etc. and only write status messages to the logs for the enabled themes
* much, much more!