Ηλίας Σταμάτης wrote [edited]:
> > what is the functionality of "admin panenl"?
> Admins can view and manage all the models of the database. Add/Edit/Delete
> users/components, etc.
as I explained, this is a very simplistic view of roles ("admins" and "users").
depending on what is being managed, different access rights apply.
the person who adds users is not the same as the person
who configures where the database is,
or the person who handled the catalog of simple components.
> > - "user management" functionality should be restricted to "user admins"
> (there is no need for a "sign up" functionality)
> So, only admins will be able to create new users?
yes, "user admins" will do user management
> Will a user be able to request an account creation?
this is not crucial nor important.
> > - "catalog management" functionality shuold be restricted to "catalog
> admins"
> What exactly to do you mean by catalog management?
copying from the wiki page:
Catalog: the set of Simple Components (with their Component Details)
that are used in the various Complex Components.
catalog management is the management of the data contained in the catalog:
adding new simple components, modifying the existing ones, deleting...
> > - whoever creates a new spreadsheet, owns it.
> So, if there's something missing I can just add it? What permissions are
> requiered in order to add a new spreadsheet?
I don't understand the "if there is a spreadsheet missing" question...
yes, obviously, if you want to create a new spreadsheet (or a word document)
you create a new one.
> For example, I'm "catalog admin" so I can create whatever component I want
> if it's missing and if I do so I'm automatically its owner. Do I get it
> correctly?
the notion of owner is more about complex components;
the catalog contains simple components.
I think you do not differentiate between Simple and Complex components...
> Is it ok to state in my application that either custom user authentication
> or an LDAP service will be used and this will be decided/discussed on a
> later stage?
it's not an either/or question, the software can easily handle both.
it's ok for the application to leave it unspecific (although it affects
the workload), but a decision on what you plan to do must have been reached
before the work starts (or at the very early stages).
--
-- zvr --
-- +---------------------------+ Alexios Zavras (-zvr-)
| H eytyxia den exei enoxes | zvr [ at ] zvr [ dot ] gr
+-----------------------zvr-+
----
Λαμβάνετε αυτό το μήνυμα απο την λίστα: Γενική λίστα αλληλογραφίας που απευθύνεται σε developers/contributors έργων ανοικτού λογισμικού - A general discussion list for developers/contributors of open-source projects,
https://lists.ellak.gr/opensource-devs/listinfo.html
Μπορείτε να απεγγραφείτε από τη λίστα στέλνοντας κενό μήνυμα ηλ. ταχυδρομείου στη διεύθυνση <opensource-devs+unsubscribe [ at ] ellak [ dot ] gr>.