Custom Query (87 matches)
Results (64 - 66 of 87)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#65 | fixed | New project doesn't show up in Labwiki | ||
Description |
as a group in iRODS, but I do not see it show up anywhere in Labwiki. When I try to create a new context, it does not appear in the drop down list. |
|||
#86 | fixed | New requirements for iRODS and git repositories | ||
Description |
Currently, the Labwiki scripts are being stored and accessed in git repositories on emmy9. This was done for at least two reasons:
One of the problems with using the git repositories on emmy9 is that users do not have access to their scripts other than through Labwiki. If they want to save them off, they have to cut and paste them from Labwiki. One of the advantages of using git is that the scripts can be versioned. However, this is not a real benefit current because the users do not have direct access to the git repository. A few options were discussed at the 4/15 meeting. This ticket will be used to track the discussions of these requirements to solve these problems. Option 1: possibly rsync git repository on emmy9 to iRODS
Option 2: dump script and config parameters to iRODS at the same time as dumping the data
Jack agreed to take a look at effort required for Option #2. |
|||
#3 | wontfix | oml2-server-hook.sh attached to tutorial instructions will not work with non-tutorial (e.g. gimiXX) iRODS accounts | ||
Description |
The oml2-server-hook.sh script that is attached to the tutorial instructions and installed on emmy9 will only push results to the appropriate account in irods if the slice name and the user's iRODS account username start with gimi[0-9]. It assumes that the zone on the iRODS server is geniRenci.
The hook script is also very specific to the configuration of the OML server in that it assumes the path to the DB file contains 12 characters. It isn't clear in the instructions that the user will need to adjust the hook script if they want to use it on their own OML server. |