Difference between revisions of "Talk:PubMan Collection Administration"
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
==Feedback on functional specification== | ==Feedback on functional specification== | ||
* | * Configarion should not be on collection level, because this might get very time-consuming for institutes, which have several collections. | ||
* | ::Not possible and will not be changed. A configuration may be taken over from another collection. The collection is the reason of having different configurations - the collection is not a "selection" of e.g. "Best of" etc.--[[User:Natasab|Natasa]] 11:02, 30 January 2008 (CET) | ||
* | * User privileges should not only be given on collection level, but also on affiliation level. | ||
* | ::Depending on what are user privileges for. See previous comment. --[[User:Natasab|Natasa]] 11:02, 30 January 2008 (CET) | ||
* It should be subject to the institute where privileges are located. | |||
::Can not understand this, if it means inheritance or not. If institute needs to have same privileges and same setup for different collections -> then in fact there is no need to have more collections then one. | |||
* The depositor should be able to define a default collection.--[[User:Natasab|Natasa]] 11:02, 30 January 2008 (CET) | |||
:: ''Comment Nicole: Already considered in current specification. --[[User:Nicole|Nicole]] 11:48, 10 January 2008 (CET)'' | |||
Latest revision as of 10:02, 30 January 2008
This page gathers feedback by the pilots and early adoptors, that was given so far and that will be given for future releases. Please feel free to add your own feedback here and sign your comments with a signature (see menu bar above).
Feedback on functional specification[edit]
- Configarion should not be on collection level, because this might get very time-consuming for institutes, which have several collections.
- Not possible and will not be changed. A configuration may be taken over from another collection. The collection is the reason of having different configurations - the collection is not a "selection" of e.g. "Best of" etc.--Natasa 11:02, 30 January 2008 (CET)
- User privileges should not only be given on collection level, but also on affiliation level.
- Depending on what are user privileges for. See previous comment. --Natasa 11:02, 30 January 2008 (CET)
- It should be subject to the institute where privileges are located.
- Can not understand this, if it means inheritance or not. If institute needs to have same privileges and same setup for different collections -> then in fact there is no need to have more collections then one.
- The depositor should be able to define a default collection.--Natasa 11:02, 30 January 2008 (CET)
- Comment Nicole: Already considered in current specification. --Nicole 11:48, 10 January 2008 (CET)