• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Work with all your cloud files (Drive, Dropbox, and Slack and Gmail attachments) and documents (Google Docs, Sheets, and Notion) in one place. Try Dokkio (from the makers of PBworks) for free. Now available on the web, Mac, Windows, and as a Chrome extension!


DSS Systems Maintenance check list

Page history last edited by Monica 4 months, 2 weeks ago

Purpose: ensure common features are operational as part of basic IR services. These may include:


Production server performance -- YING

  • Per recommendation by Campus IT, perform monthly clean up of the bots. See lighthouse ticket #1053 for more details.


Linux server reboot -- YING/SID

  • Campus IT will perform weekly maintenance on RDSA Linux service each Tuesday 8am-9am. Programmers should be available to address any issues. Reboot should not take longer than 15 minutes. During this time RDSA will be offline. (effective July 2021)


ETDs push to ProQuest -- SID


  • annually in June or whenever requested by GPS
  • Check in with Kate to notify before work goes out 
  • Notify Kate and CDS team when complete 


Web Site availability  -- YING/SID


Website Accessibility 

  • confirm https://scholarship.rice.edu/ site including common pages (item, collection landing, search results, browse by, etc.) confirm to WCAG AA level


Security -- YING/SID

  • Preventative activity 
  • not an automatic process, need to monitor environment for security updates.
  • check for updates manually and makes changes as needed


Media Filter --YING/SID

  • Confirm media filter runs overnight (e.g. extract full text and create thumbnail)
  • Set up DSpace System Email for when exceptions occur
  • Produced media log separately so is easier to check 


CheckSum report -- YING/Staff


Statistics logs -- YING

  • Ensure data is captured daily
  • Create script to check update of the index on daily basis


File Format registry  -- MONICA 

  • Annually check for "unknown" file types and make assessment for preservation level and update Format registry 


Metadata -- MONICA

  • Annually check for consistency of IR metadata (types, rights, dates, etc.)


Index -- ???


Run Dspace health check -- ???


Duracloud -- SID

  • Report total storage usage 
  • Perform transfer of files twice a year. Identify dates???
  • see notes on Digital Preservation Storage Actions and Policies on Staff Wiki (log in required). 


Additional backup -- ??? 

  • OLD --
    • Twice a year or before any significant programming updates (e.g. new software release, hardware changes, etc.)
    • Ying investigating if still useful given new Isilon Server setup 
  • Create a complete copy of Production to Development server to mirror all content (files, metadata and system settings). -- is this still a practice?
  • Backup of DSpace server and logs -- is this automated now?
  • see Isilon Storage parameters 


Handle system -- SID

  • happens when re-boot the system, have to manual re-boot handle server
  • Sid to look if can automate re-boot process


OAI data provider - MONICA


Untrusted site security certificate -- SID

  • every three years, request new certificate (Sept/Oct)
  • next schedule 2020 (Sept 19)
  • see lighthouse ticket for history #26


Vireo -- SID

  • check that server is not nearly out of local storage: df < 90%


Omeka -- YING


Jstor Forum -- MONICA

  • check storage usage is less than 1TB 


Google analytics  -- SHANNON / MONICA

  • Periodically share top results from Google analytics report
  • Confirm google index is current
  • Spot check indexing of titles
  • see notes for Ensuring your DSpace is indexed


Sword deposits -- SHANNON / YING

  • Confirm biomed auto-deposits is working


Harvey Memories, COVID-19 archives - YING



Ad hoc issues -- SID

  • hostname resolver  (e.g. dspace.rice.edu vs. scholarship.rice.edu)
  • jp2 viewer resolver (confirm viewer is working properly)



  • If need immediate response to issues, may need to reboot server during peak hours. First Send notice to internal users before re-boot
  • For non critical updates, may wait to reboot after 5pm (no general notice need be sent)
  • IR Maintenance Reporting - First Monday ea. month (DSS staff to check BEFORE meeting)
  • For public presentations of the IR, please notify programmers to avoid any system downtime



Comments (1)

Monica said

at 3:46 pm on Nov 26, 2013

tinyurl to this page http://tinyurl.com/p3bh9ns

You don't have permission to comment on this page.