Mounting-Project-Spaces.md

-What's described here is a standard method for bring some order to the chaos of project data locations on campus.  The basic idea is there is a single root directory that contains links to local project data you care about.  Once filesystems are linked in a standardized way, your software can use these canonical paths instead of the actual locations to access files from programs and scripts.  A level of indirection isolates code from the storage-relocation churn.
+What's described here is a standard method for bring some order to the chaos of project data locations on campus.  This is file-sharing as infastructure, and is targeted towards sharing large datasets.  For one-off files such as copies of Word documents, the one-drive system and e-mail work well.
 
-## A setup procedures for Windows
+The basic organizing idea is there is a single root directory that contains links to shared project data and installed libraries that you care about.  Once filesystems are linked in a standardized way, your software can use these canonical paths instead of the actual locations to access files from programs and scripts.  Adding a level of indirection isolates code from the storage-relocation churn as servers are enabled and disabled.
+
+## Procedure for Windows
 
 You will need administrator access for step one of this procedure.  Afterwards your standard login will work.
 
-1. 
+1. Your regular user account will be using the Windows command
+   [mklink](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink) 
+   to provide access to the remote space.  Log in as your admin account and open the
+   group policy editor.  This can be done with the command:
+   ```batch
+   > sepol.msc
+   ```
+   if you don't feel like traipsing through GUI menus.  Navigate to "Local Policies" -> 
+   "User Rights Assignment" and click "Create Symbolic Links".  Then add your regular
+   user account to the list.  After setting policy, **reboot** your computer.
+  
+2. After reboot, login as you're normal, non-admin account.  Then issue a command similar
+   to the following, examples for the Juno and Cassiope missions are given below.
+   ```batch
+   > mkdir C:\project
+   > mklink /d C:\project\juno \\melmac.physics.uiowa.edu\project\juno  
+   > mklink /d C:\project\cassiope \\rdss.uiowa.iowa.edu\rdss_dmils\MGF
+   ```
+   You will of course have to have access to the server in question in order to create
+   the link.  For the examples above talk to Larry Granroth for Juno, and David Miles 
+   for Cassiope.
+
+Note on the use of `/d`.  The windows `mklink` command can create three different types
+of links.  Directory links (/d) are the most forgiving.  You computer will run just fine
+if the upstream server is not available.
 
-## Access procedures for Linux
+## Procedure for Linux
+TODO
 
-##
\ No newline at end of file
+## Procedure for MacOS
+TODO
\ No newline at end of file