Difference between revisions of "Archive - Curricular Applications Overview"
From Help Wiki
(Created page with '===Context=== #'''Moodle Courses''': #:'''''yearly archive''''' #*Will have single curricular instance (may have other instances for Groups) #*after 120 days of inactivity st…') |
|||
| Line 24: | Line 24: | ||
#*'''Group WordPress sites''' will remain available as long as one member has a current Evergreen login. Group members are responsible for making sure they have active users to maintain the longevity of a site. | #*'''Group WordPress sites''' will remain available as long as one member has a current Evergreen login. Group members are responsible for making sure they have active users to maintain the longevity of a site. | ||
#'''Portfolios''' | #'''Portfolios''' | ||
| − | #: | + | #:Are not currently archived. |
#'''Email Lists''' | #'''Email Lists''' | ||
| − | #: | + | #:Email lists are currently not archived. A list often remains idle until the Faculty member needs it again. If a list name is transferred to another Faculty member the prior content is not necessarily saved. |
#'''Program Shares''' | #'''Program Shares''' | ||
#: Completed academic program shares will be removed from \\orca\programs every quarter. A short term archive (STA) folder will house the completed program shares that are one quarter old. This will not be a shared directory but available only to staff. The archive schedule will be as follows; | #: Completed academic program shares will be removed from \\orca\programs every quarter. A short term archive (STA) folder will house the completed program shares that are one quarter old. This will not be a shared directory but available only to staff. The archive schedule will be as follows; | ||
Revision as of 16:26, 19 November 2010
Context
- Moodle Courses:
- yearly archive
- Will have single curricular instance (may have other instances for Groups)
- after 120 days of inactivity students will expire out
- by August 1st course is moved to archives category, students will lose access to course instance, Faculty will continue to have access
- sitetracker will rename course name to coursename + term + year + "archive"
- sitetracker will clean up stubname in preparation for creating user-friendly backup filename
- after 2 years expire faculty from the course???
- Deep Archive:
- will be stored in /sauk/files/archive
- Hosted sites on Coyote:
- By July 15 these sites will be moved to archives.evergreen.edu/curricular and organized by year-based directory structure. Sites created prior to the 2009-2010 academic year will also be moved to archives.evergreen.edu/curricular/and organized by year-based directory structure.
- Drupal Sites:
- The remainder of these sites will be scraped into a flattened HTML format and posted to archives.evergreen.edu/curricular and organized by year-based directory structure.
- MediaWiki Sites:
- These sites will be scraped and flattened by July 15 and sent to archives.evergreen.edu/curricular and organized by year-based directory structure. The suffix _wiki will be added to the top level of these sites in the event the program had multiple resources of the same name.
- WordPress Sites:
- Curricular WordPress sites: These sites will be scraped and flattened by July 15 and sent to archives.evergreen.edu/curricular and organized by year-based directory structure. An XML export will also be created and kept with the files in the event faculty want to recreate the site in WordPress (images and attachments are not stored in this file). Faculty will be notified prior to the site being deleted. In the event faculty want to continue using the site for a continuing year, the site will be left live (an archive copy of the past year will still be created).
- Note: curricular sites should be scraped before individual student blogs are deleted to capture any student work linked to from the curricular site.
- Individual WordPress sites are currently only available for the lifespan of an Evergreen login. We will work to better educate students about the limited life-span of their blogs and provide options for what to do with their blog after Evergreen. This could include adding information about blog longevity to the blog creation form and to the letter that goes out to students regarding their account deactivation. When the disabled accounts list becomes available we will disable all blogs associated with these accounts. We will then run an xml export on these blogs before deleting. These exports will be used in the event that a student needs access to the content of their blog. We will store these xml files for ?
- Group WordPress sites will remain available as long as one member has a current Evergreen login. Group members are responsible for making sure they have active users to maintain the longevity of a site.
- Portfolios
- Are not currently archived.
- Email Lists
- Email lists are currently not archived. A list often remains idle until the Faculty member needs it again. If a list name is transferred to another Faculty member the prior content is not necessarily saved.
- Program Shares
- Completed academic program shares will be removed from \\orca\programs every quarter. A short term archive (STA) folder will house the completed program shares that are one quarter old. This will not be a shared directory but available only to staff. The archive schedule will be as follows;
- Each quarter week 2: The existing contents of the STA folder are purged and the previous quarter programs that are completed are moved to STA folder. This will enable AC staff to quickly restore data from the previous quarter upon request from students and faculty. After one quarter, restore requests will get funneled through Academic Computing staff to Network Services to perform a restore from tape.
- September 1: All completed program folders from the previous academic year (including summer) will get moved to STA to provide clean slate for new program shares at the beginning of fall quarter
- Completed academic program shares will be removed from \\orca\programs every quarter. A short term archive (STA) folder will house the completed program shares that are one quarter old. This will not be a shared directory but available only to staff. The archive schedule will be as follows;
