I think it would be better to have one project per experiment. Make sure to always have the correct project activated when you create items and they will automatically be shared to that project.
Manual sharing is only needed for items that are used in multiple projects, typically labels, protocols, scanners, etc. But that is usually done on the group-level (eg. to the EVERYONE group). Of course you may do as you outline below, but I think it will generate a lot of manual work when moving stuff between projects. The four "projects" you mention below would probably work better as groups. If you have a one-project-per-experiment approach you can then simply share that project to the correct group. /Nicklas Moore, Jonathan wrote: > Hello, > > I am thinking about how to use BASE to manage data release, and I have > come up with the following process. > > Several projects, with increasing numbers of members, e.g.: > > Development > Evaluation > Production > Release > > Generally we will model an experiment in the Development project first, > share it with the Evaluation project for quality checking, when it is > checked share it with the Production project, and when it is ready for > public release share it with the Release project. Updates will be > possible from the Development project, but not any of the others. > > My questions is about the best way to approach the setting of privileges > and what to share and when. > > Should we share every object individually, or will shares be inherited > if we just share an experiment once it has been validated? Sharing works on individual objects only. It is not inherited. There is one exception: Sharing a directory can also share all subdirectories and files in that directory. > Do we have > to share objects which are not strictly part of an experiment, such as > each protocol, individually? It is better to share such things to the EVERYONE group. > Is there any way to tell whether > everything that is needed has been shared? You can use the "Experiment overview" function (select a single experiment and the click on the "Overview" tab). It will display warnings for all items that the currently logged in user doesn't have access to. But this user can of course not fix the permissions so you'll need to login as a different user with proper permissions to fix it. But this user doesn't get the permission warnings so you may have to work with two different windows. > Many thanks. > PS I have posted a ticket on a bug I came across trying to accomplish this. Can you please check your bug report and clarify some things. There is no "Project summary" in BASE. /Nicklas ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to basedb-users-requ...@lists.sourceforge.net
