Difference between revisions of "SUNScholar/Customisation"
m (→SOFTWARE DEVELOPMENT)
|Line 56:||Line 56:|
Revision as of 02:29, 23 December 2016
- 1 EIFL Webinar
- 2 SOFTWARE DEVELOPMENT
- 3 OPERATIONAL GUIDE
- 4 CUSTOMISATION SCOPE AND CAPACITY
- 5 README FIRST - Advanced Feature Customisation (Modules Overlay Method)
- 6 Introduction
- 7 Director/Manager
- 8 Librarians
- 9 Interoperability
- 10 Mailing Lists
- 11 References
- 12 DSpace References
Click on the heading above,
This customisation relates to the technical details involved in the customisation of features available with DSpace, not the customisation required when performing operational management of the research archive. For example, the creation of communities and collections is for the repository director/manager to determine. See: http://scholar.sun.ac.za for an example of a communities and collections hierarchy.
CUSTOMISATION SCOPE AND CAPACITY
If the feature customisation is to be preserved on the repository system for the long term, then adequate resources must be provided to ensure continuity of the customisation during system upgrades. Depending on the amount of customisation, this could turn out to be VERY EXPENSIVE for the institution if using an external service provider and if upgrades are done on a yearly basis. Therefore, the rule of thumb, for resource scarce institutions that do not have the system capacity, is to keep customisation to the ABSOLUTE MINIMUM or acquire the resources to build adequate system capacity locally in-house.
README FIRST - Advanced Feature Customisation (Modules Overlay Method)
Please read about advanced customisation before starting any customisation work, as it is the basis for most of the customisation tasks.
The idea is to put all your customised code into the folder:
The source code is copied from the folder:
This allows you to keep the source code intact and to keep your modifications in one separate place. Using this method also helps greatly during upgrades.
Also please note, that to apply these customisations you will usually have to rebuild DSpace.
See the official explanation below:
All of the feature customisation and system administration documentation assumes:
- That DSpace has been installed according to: http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace.
- That you are working as the "dspace" user, which was created during the installation of the Ubuntu server software.
Now that you have a working repository, you will probably want to make it your own using a proper change management system.
Below are links to help pages with detailed information on how to customise your repository, to make it fit for the purpose for which it was created.
For more information consult the official DSpace documentation and subscribe to the DSpace help mailing lists (see bottom of page below) so that you can ask the experts for help.
Before beginning customization using this guide, please familiarize yourself with command line editor, nano. See below for brief instructions.
- NANO Editor Help
|CTL+O||= Save the file and then press Enter|
|CTL+X||= Exit "nano"|
|CTL+K||= Delete line|
|CTL+U||= Undelete line|
|CTL+W||= Search for %%string%%|
|CTL+\||= Search for %%string%% and replace with $$string$$|
|CTL+C||= Show line numbers|
More info = http://en.wikipedia.org/wiki/Nano_(text_editor)
- Browse and Search Indexes
- Usage Statistics
- Media Filters (Item full text search and thumbnails)
- Digital Object Checksums
- Digital Object Identifier's
- Harvest Remote Collections (OAI Consumer)
- Allow Remote Harvesters (OAI Producer)
- Allow Remote Deposits (SWORD interface)
International DSpace Support
Before posting a request, please see: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette first.
African Repository Support
Click on the heading above.