search

eXist-db / tamboti

Tamboti Metadata Framework: framework for cataloguing bibliographical material and other resource types such as web sites, images and videos.
1 stars 8 forks source link

"create new folder" results in "parsererror"; NEW folder not visible #73

Open jodevelops opened 11 years ago

jodevelops commented 11 years ago

When creating a new folder, i get an error instead of my new folder:

(the folder created was entitled "testfolder-1 within "Samples")

25-11-2013 15-14-33

However, as soon as a SECOND folder is created, BOTH are visible/ accessible, etc.:

25-11-2013 15-20-19

This may have to do with #30

claudius108 commented 10 years ago

This is due to the fact that, for solving https://github.com/eXist-db/tamboti/issues/28, I had to use function sm:get-account-metadata() [1], which did not specify that the user has to be in DBA group, in order to get other accounts' metadata.

So, we do have to sacrifice the showing of real names, unless we can execute this function as admin (or so), or grab that metadata from somewhere else.

Thoughts?

[1] http://exist-db.org/exist/apps/fundocs/index.html

jensopetersen commented 10 years ago

If it is grabbed from somewhere else it will need to be updated all the time, which is not good. Dulip, what do you think about hard-coding the admin password?

claudius108 commented 10 years ago

Or, I guess (as this has to be tested), one can add the "editor" user to "dba" group during installation of tamboti, but this would limit the user installing tamboti to users belonging to "dba" group.

withanage commented 10 years ago

Claudius, I mailed you and jens the suggestion. Adding editor to the dba group, is not so handy, cause it will give the editor the access to other areas. I would sepearate app user groups from dba.

claudius108 commented 10 years ago

Hm, on the other hand, this would mean that third parties installing tamboti, would have to hard-code the admin password, too?

withanage commented 10 years ago

Not really, It must not be the admin password, it should be any user with admin rights for executing db functions. Difference is, it is not the user, but the group which controls the access in tamboti and wiki : non-admin group for apps and resources and the users in that group get reading access to apps and resources. Admin user binding for executing dba-functions if necessary. Would have been better, if certain database functions could be assigned to a group other than dba user. But that is a discussion, which should go to eXist mailing list.