Hi Irene,
We've wondered that too at my university, Ohio State University, so we've
upped our setting to 600 which we feel is safe, but users typically do
smaller batches.
I'm guessing the too-low-for-practical-use limit of 20 is to be overly
conservative by default, so that there is no risk of data loss or
interruption.
Doing batch changes with a large number of changes will keep your system
busy, and the reindexing can take a while. I've noticed that when we set the
limit to be really high, it appears that nothing will happen from the user's
browser for 20+ minutes, so I've connected to the server from the command
line, and noticed that the reindexing task was taking a long time, but still
running. So you might be safe with setting this to a really high number
(several thousand), you'll just have to have the patience to not disrupt it.
But smaller / more manageable batch sizes will complete in a reasonable
amount of time. With this set to 1000 or more, I'm guessing your more likely
to run into Out-Of-Memory errors
There is a note in:
https://wiki.duraspace.org/display/DSDOC/System+Administration#SystemAdministration-BatchMetadataEditing
that
cautions against doing too large of batch edits.
Peter Dietz
On Wed, Jul 27, 2011 at 5:25 PM, Berry, Irene (CIV) <icbe...@nps.edu> wrote:
> Hello,
> We're experimenting with making batch corrections to metadata using the
> Import Metadata feature in the jsp. We'd like to raise the limit on the
> number of items that may be changed at a time.
>
> I can see the file:
> http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.2/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/servlet/MetadataImportServlet.java
>
> Where it says this:
> // Set the lmimt to the number of items that may be changed in one go,
> default to 20
> limit = ConfigurationManager.getIntProperty("bulkedit.gui-item-limit", 20);
> log.debug("Setting bulk edit limit to " + limit + " items");
>
>
> …We’d like to up it from 20 to maybe 500 as an experiment -- but
> potentially much higher. Does anyone know if that's a really bad idea? We
> just don’t know what the consequence is of making this limit larger, but 20
> seems way too low for a typical batch of changes.
>
> Thanks,
>
> Irene Berry, MLIS
> Digital Services Librarian
> Dudley Knox Library, Naval Postgraduate School
>
>
>
> ------------------------------------------------------------------------------
> Got Input? Slashdot Needs You.
> Take our quick survey online. Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
