Thanks Tim. Right enough- that worked! Some dodgy data cascading through
the item2bundle, bundle, bitstream2bundle and bitstream tables, which I
have been able to remove. Glad that it wasn't anything more complex.
Cheers again
Scott
On Wed, Sep 12, 2018 at 3:26 PM Tim Donohue wrote:
> Hi
Hi Scott,
Looking at that migration script, I see two possible ways this might be
occurring...
Take a look at the full context of the changes to the `bundle2bitstream`
table:
Hi GG,
At this time DSpace doesn't have a way to automatically move Items from one
Collection to another during the submission or approval process.
I suspect the easiest way to accomplish this might be to simply ingest this
files into your "review" Collection (you can even setup this Collection
Before you can batch import files (including PDFs), you need to create or
provide metadata that describes those files. DSpace is currently not able
to auto-extract metadata from PDFs, so metadata must be provided as part of
the bulk import package.
Often, the easiest way to bulk ingest any files
All-
At our institution we'd like to set up a workflow where items are ingested
into a single 'review' DSpace collection (from Symplectic Elements), then
moved into another collection by a metadata reviewer as they're approved.
Is there any way to do this through the Item submission
Hello everyone,
I am trying to enable authority control for a keyword field on DSpace 6.3 -
Mirage2 interface, but I am lost.
Could someone please guide me through the configuration? First of all, what
plugin should I select and configure?
The goal is to help submitters select keywords by
Dear All,
I'm having trouble using the automatic harvest scheduler both in the XMLUI
and in the command line. The version of DSpace the server is running on is
6.3. When I use the command line (dspace harvest -S), the command line
returned the following error:
Starting harvest loop...
