[DS-703] Making the OAI max amount of records configurable

git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5428 9c30dcfa-912a-0410-8fc2-9e0234be79fd

dspace-oai/dspace-oai-api/src/main/java/org/dspace/app/oai/DSpaceOAICatalog.java

@@ -96,7 +96,7 @@ public class DSpaceOAICatalog extends AbstractCatalog
             + ConfigurationManager.getProperty("dspace.hostname") + ":";
 
     /** Maximum number of records returned by one request */
-    private final int MAX_RECORDS = 100;
+    private final int MAX_RECORDS = ConfigurationManager.getIntProperty("oai.response.max-records", 100);
 
     public DSpaceOAICatalog(Properties properties)
     {

dspace/CHANGES

@@ -42,6 +42,9 @@
 - [DS-698] Clear primary_bitstream_id references when deleting a bitstream
 - [DS-696] Reduce cost of browse index pruning
 
+(Ben Bosman)
+- [DS-703] Making the OAI max amount of records configurable
+
 1.6.2
 =====
 

dspace/config/dspace.cfg

@@ -1847,9 +1847,7 @@ webui.suggest.enable = false
 # plenty of memory, at least 512 MB to your Tomcat.
 #
 # Optional: DSpace uses 100 records as the limit for the oai responses. You can
-# alter this by changing $DSPACE_SOURCE_DIR/src/org/dspace/app/oai/DSpaceOAICatalog.java to modify the
-# declaration:
-# private final int MAX_RECORDS = 100 to private final int MAX_RECORDS = 30
+# alter this by changing oai.response.max-records to 30.
 # oai.didl.maxresponse = 0
 
 # When exposing METS/MODS via OAI-PMH all metadata that can be mapped to MODS
@@ -1858,6 +1856,10 @@ webui.suggest.enable = false
 # hide this information set the following property to true
 oai.mets.hide-provenance = true
 
+# DSpace by default uses 100 records as the limit for the oai responses.
+# This can be altered by enabling the oai.response.max-records parameter
+# and setting the desired amount of results.
+oai.response.max-records = 100
 
 #---------------------------------------------------------------#
 #--------------SWORD SPECIFIC CONFIGURATIONS--------------------#