Final Notes
Extra challenges
Some more exercises for the ones that need a little extra challenge:
- Can you find the hidden file??
- You can read it, but you have to search for a file tagged as 'secret'...
- Can you add the metadata: metadataname: yourname, metadatavalue: "I found it!".
- Can you find how many people have a dataset called iris.data (that you are allowed to see)?
- Can you make a query to figure out all the total size of all the files that you have access to, grouped by directory!
Not discussed
The irods rule system and PEP's
In the course you saw an example of an irods rule implemented by us to automate certain data tasks. iRODS has a system where you can implement automation in either a separate rule, or incorporated into the irods structure.
This is a bit beyond the content of this course, but is something we are doing. For example, we implemented a PEP(policy enforcement point) that will check for every upload whether the file does not have special characters in it. This is because iRODS enables us to implement a piece of code that will be run before or after uploading data. They have a lot of these policy points that we can use to autiomate or check things after or before certain actions like updating metadata, uploading, changing access, etc. Because this is a complicated process to design and it has to be done from within the server these are actions we will not discuss here.
iRods documentation/community
For more advanced usage and customization, refer to the iRODS 4.3.2 documentation and the iRODS community resources.
Course feedback
Can you fill in this form about the course?