Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F67473999
table-structure.html.wml
No One
Temporary
Actions
Download File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Subscribers
None
File Metadata
Details
File Info
Storage
Attached
Created
Sat, Jun 22, 15:10
Size
3 KB
Mime Type
text/x-c
Expires
Mon, Jun 24, 15:10 (2 d)
Engine
blob
Format
Raw Data
Handle
18413799
Attached To
R3600 invenio-infoscience
table-structure.html.wml
View Options
## $Id$
## This file is part of the CERN Document Server Software (CDSware).
## Copyright (C) 2002, 2003, 2004, 2005, 2006 CERN.
##
## The CDSware is free software; you can redistribute it and/or
## modify it under the terms of the GNU General Public License as
## published by the Free Software Foundation; either version 2 of the
## License, or (at your option) any later version.
##
## The CDSware is distributed in the hope that it will be useful, but
## WITHOUT ANY WARRANTY; without even the implied warranty of
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
## General Public License for more details.
##
## You should have received a copy of the GNU General Public License
## along with CDSware; if not, write to the Free Software Foundation, Inc.,
## 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.
#include "cdspage.wml" \
title="WebAccess Table Structure" \
navbar_name="hacking-webaccess" \
navtrail_previous_links="<a class=navtrail href=<WEBURL>/hacking/>Hacking CDSware</a> > <a class=navtrail href=<WEBURL>/hacking/webaccess/index.html>WebAccess Internals</a> " \
navbar_select="hacking-webaccess-tabfill"
<p>Version <: print generate_pretty_revision_date_string('$Id$'); :>
<pre>
Explanation of the WebAccess table structure and how to create authorizations.
-- accROLE --
roles are collections of authorizations within specified areas. these should
have a clear connection, for example within a module or for a special type of
person, e.g a library administator.
id - specify the id of the role
name - unique name for the role
description - describe the authorization tasks the role will cover
-- user_accROLE --
give users access to the authorizations/actions provided by the given role.
id_user - id of user in the database, usually just the supportemail and/or adminemail
id_accROLE - id of role from accROLE
-- accACTION --
the actions specify what information is needed to create an authorization.
an action can take any number of arguments, and you also have the possibility to
make these arguments optional.
id - specify the id of the action
name - unique name for the action
description - describe authorization area
allowedkeywords - the keywords for the wanted arguments
optional - enum to define wether arguments can be optional
value: ['yes', 'no']
'no' - action without arguments or not optional arguments
'yes' - only actions with arguments
-- accARGUMENT --
arguments for the authorizations. one entry might be shared by several authorizations,
so it is important to not change these but simply add new ones when a change is needed.
id - id of the argument
keyword - the one listed in an action's allowedkeywords
value - the value connected to the keyword in an keyword=value argument pair
-- accROLE_accACTION_accARGUMENT --
ternary connection to create authorizations. when an authorization has more than
one argument they need to be connected somehow. the same id for role, action and
argumentlist does this. there must be at least as many entries as allowedkeywords
for the action. with more entries all authorizations are found using a cross product.
id_accARGUMENT and argumentlistid are both set to 0 when the action have no arguments.
with optional arguments they are both set to -1.
id_accROLE - reference to argument in table accROLE
id_accACTION - reference to argument in table accACTION
id_accARGUMENT - reference to argument in table accARGUMENT
argumentlistid - glue to bind entries into authorizations.
</pre>
Event Timeline
Log In to Comment