Background document describing the current configuration: https://docs.google.com/document/d/1qTV4vMTGZe4lqRrhrtNZVXik1T80JdeYDxv7JdusWy8/edit#heading=h.r8jwzqgei0qe
...
- Issue with AD groups vs Isilon shares
- Vetting vs. adding/removing people
- View only access to AD Groups?
- Clean up needed
- Isilon
- Ongoing false alarm issue —> changing the Infiniband
- Finalizing the reorg of the Isilon to have a “human free” preservation area
- Tim’s scripts…
- Other items including big picture / policy aspects: see "Digital Preservation Infrastructure Development: Where we are &Planning for the next Steps"
...
- When new people start or if people need access to something that they didn't have access to. Or every time a new student worker starts
- Each time a new share is created, Tamar creates several AD groups; 1 that is read/write and 1 that is read-only
- Over time, some Shares got renamed, but the AD groups did not get renamed, so now there is a disconnect between names of shares and names of groups.
- There also hasn't been a cleanup of users who are no longer here.
Tim's time allocation
- Chad should talk to Tim and make sure that this work still makes sense with our immediate or long term goals for the Isilon.
- Someone will need to be designated to work with Tim and to take responsibility for what is on the Isilon and make sure that everything is where it should be and how it should all be structured.
- Once Delphine leaves, there is no one person who knows all the ins and outs of the structure of the Isilon.
- This may be multiple people moving forward. And we will need to use Jira to document and track.