Rising For Justice’s plan to store files in O365
We are in the process of migrating your data from Google Drive to Microsoft’s O365. This data migration involves not just moving files in the way they are currently organized, but also reorganizing them to better reflect your needs.
Much of the data currently in Google Drive developed from the user upward, with staff creating documents in their own Google Drives and then sharing it with others. This has resulted in some disorganization of RFJ files and has sometimes made it difficult for you to find files or know who owns them.
Once the files have been migrated to O365, we will be storing them in shared libraries based on related project and/or company department.
This article defines the plan that will be implemented to structure the data in O365.
Microsoft’s cloud based services solution, provides two applications (apps) for storing and accessing RFJ’s data: SharePoint and OneDrive. This article (including attached posts) will introduce you to these apps and guide you as use them effectively, efficiently and consistently. This consistency will keep the data organized so that you and your fellow staff members can easily store and find data now and moving forward.
This article will teach the features of these apps relevant to this plan. it is not an attempt to teach all features of these apps. In fact, we encourage you to only use the features described in this article as we perform the migration. Post migration, additional features will be added.
Please review this article in its entirety to make sure you are familiar with this plan before starting to use these apps.
Upon first review of this article, we recommend reading the posts in order. Thereafter, you may want to jump around while you are refreshing your memory about a particular subject.
Article Index:
Initial Setup:
Sending/Receiving files:
IMPORTANT!
The plan outlined in this article does not utilize all of the features of either OneDrive or SharePoint. It purposely limits the features in order to:
- Adhere to best practices
- Streamline the operations
- Make it easier for staff to learn
- Keep the organization of data more structured, and therefor easier to implement and maintain
- Omit features with less benefits
We strongly encourage users to stick to the operations of the plan outlined in this article until the plan is enhanced. Clicking on other links and using additional features can easily have deleterious effects. If you are interested in additional features, please reach out to your supervisor and/or administration before trying them.
We ask you specifically to avoid doing the following:
- Please do NOT add additional sites or libraries without reviewing the need to do so with your supervisor and/or administrator.
- Please do NOT sync folders or libraries to your computer. We will be doing this at a future stage, but doing so during the migration can have negative repercussions.
This page was developed specifically for RFJ, and the URL is not published. The attached posts will open in a separate tab in your browser, allowing you to return to this page by clicking the original tab. You can also return to this page by entering the RFJ URL again (https://hdf.net/rfj-fsp/).
If you have questions about this, please let us know and we will be happy to assist you.
Take care,
