Skip to end of banner Go to start of banner

User

Skip to end of metadata

Created by Darya Tarasowa, last modified by Roy Meissner on Aug 05, 2016

Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Responsible: Kurt Junghanns

objectid = {
	type: 'string',
	maxLength: 24,
	minLength: 24
};

user =

property	type	required	format checking	state of implementation
_id	integer, autoincrement	yes	isInteger	autoincrement - not implemented
email	string	yes	isEmail, unique	unique - not implemented isEmail - controlled by ajv
username	string	yes	unique	unique - not implemented
password	string (contains SHA512)	yes	alphanumerical	hash is generated on frontend
defaults	objectId	no	is integer, preference object exists with such id	not correctly implemented for now should decide on the preferences data model,
registered	date	yes	date	need to decide on the date format
surname	string	yes		implemented
forename	string	yes		implemented
gender	'male', 'female', null	no		null value should be possible
locale	string	yes	one of the available locales	need to decide on the locale format
hometown	string	no		implemented
location	string	no		implemented
languages	array of locales	no	locales (like above)	see locale
picture	string	no		implemented
interests	array of strings	no		implemented
description	string	no		implemented
birthday	date	no	date	implemented
infodeck	objectId	no	isInteger, deck exists with such id	implemented

Not yet implemented: preferences =

property	type	required	format checking	state of implementation
_id	integer, autoincrement	yes	isInteger
language	string	yes	isValidLanguage
theme	objectId	yes	theme exists with the id

No labels