UPDox: Difference between revisions
From Iskomunidad
| Line 14: | Line 14: | ||
=Documents= | =Documents= | ||
* UPDox supports a wide range document types. | * UPDox supports a wide range of document types. | ||
* Recommendation: Ultra-sensitive documents passed through the Repositories should be encrypted by tools like [http://www.truecrypt.org/ TrueCrypt]. (It's only the "ultra" ones that should be doubly secured, since UPDox already has its own security measures.) | * Recommendation: Ultra-sensitive documents passed through the Repositories should be encrypted by tools like [http://www.truecrypt.org/ TrueCrypt]. (It's only the "ultra" ones that should be doubly secured, since UPDox already has its own security measures.) | ||
<br /><br /> | <br /><br /> | ||
Revision as of 11:28, 12 April 2013
UPDox (updox.upd.edu.ph) is a document management system for the UP faculty and some UP offices. Run by DILC, UPDox uses Alfresco and other document collaboration, version control, and file sharing systems. Priority is given to official, University-related use.
To request access accounts, email dilc@dilc.upd.edu.ph.
Access
- Within Dilnet: you may have to set proxy exception for the UPDox address.
- Make sure port 8080 is useable.
Repositories
- Collaboration via Git-like repository. Codes, non-large documents (preferably <10MB a file) may be consolidated directly from users' desktops or access devices.
- Direct within team sharing of large files a la peer-to-peer torrent.
Documents
- UPDox supports a wide range of document types.
- Recommendation: Ultra-sensitive documents passed through the Repositories should be encrypted by tools like TrueCrypt. (It's only the "ultra" ones that should be doubly secured, since UPDox already has its own security measures.)
Backup
- For those using its Repositories, UPDox is already a form of a backup.
- Yet, UPDox is still backed up in a off-site facility, making the system more disaster-resistant.
See Also
- Obletorr-Ikot
- DILC:UPDox Admin Notes (DILC Staff Only)