A digital repository should be flexible in the types of documents it accepts (e.g., working papers, peer-reviewed materials, technical reports, presentations for the lay community, etc.), the paths to publication (self-publishing by authors vs. gatekeeping by site administrators), and the structure of the participating publication series (i.e., can individual departments or research units customize their space within the repository). Digital Commons@ allows for this flexibility, and also provides a wealth of key features:
- Automatic conversion of documents to PDF
- Ability to publish HTML
- Ability to publish non-static resources such as sound and video files, data sets, and executables
- Full-text searching
- Saved Searches
- Personalized email notification of newly published content
- Browsing by date or author
- GUI-based template editor
- HTML-based templates
- Customized controlled-vocabulary picklists for data entry
|
- Site customization at any level
- Auto-image generation
- Branded publication sites for participating research units
- Automated email interface between author and publication administrator
- Usage statistics at the publication and paper level
- Flexible document hierarchy
- "Push" email capabilities
- OAI compliant
- Data exporting as XML
- Data transfer to third party indexing services
|
Furthermore, Digital Commons@ licenses include hosting, offsite backup, technical support, training, and upgrades to the software. Ownership of all content is maintained by the licensee. To learn more about licensing opportunities, please email us.
A Note about Open Source vs. Commercial Implementations
"Open source" is a slightly misleading term. It suggests that the system is free. However, the hardware needed to house it, the staff needed to maintain it, the development resources needed to adapt it to a specific community's needs, and the technical support team needed to address user questions amounts to a substantial financial commitment. By way of illustrative example, MIT, with 9,200 faculty and staff and 1 campus, will spend more to support its open source implementation than the University of California, with 10 campuses and 159,000 faculty and staff, pays The Berkeley Electronic Press to operate its repository.