On Mon, Oct 21, 2013 at 2:34 AM, Gary Browne <gary.bro...@sydney.edu.au> wrote: > It looks like this is not possible with the wildcard policy tool, as > BITSTREAM seems to cover thumbnails, previews and images - so one cannot > differentiate between them.
True, wildcard policy tool is handy, but not too fine-grained. > Is it the case that I would need to write some SQL to do this (it could be > done by hand, but my repository manager doesn't want to go through ~500 > records and do this - don't know why)? If so, would the policies just be > overwritten by DSpace? What are the alternatives? Yes, SQL is the way to go. It's quite straightforward, although there are many joins involved (to limit to a particular collection and to limit to bundles with particular name) - or, if you have the list of bitstream_ids it's trivial. let me know if you need specific help. DSpace won't overwrite your policies unless you run the wildcard policy tool again on the collection on bitstreams. As usual, don't forget to backup the database before changing anything in it. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
