Jose,
I am running this on a live instance which has not been announced
publicly yet (though it is accessible). I'm not worried about people
seeing things appear and disappear as I import, delete and re-import,
because no one is actually using the site yet. The files import fine,
just without descriptions. Unfortunately, the descriptions are very
important because each item has multiple files.
Thanks for spotting the bug in the code. I was afraid that was the problem.
-Josh
On 10/25/2011 04:17 PM, Blanco, Jose wrote:
Josh,
I think there may be a bug I the code. If you go to ItemImport.java
and look at the method processContentsFile, you will see something
like this:
registerBitstream(c, i, iAssetstore,
sFilePath, sBundle);
System.out.println("\tRegistering Bitstream: "
+ sFilePath
+ "\tAssetstore: " + iAssetstore
+ "\tBundle: " + sBundle
+ "\tDescription: " + sBundle);
I think that the description is not being grabbed to generate the
output you are seeing, but instead it is displaying the bundle for the
description, as you are seeing. But I think the item should get into
Dspace just fine from looking at the rest of the code. You are doing
test run on this right? So you are actually not putting anything in
your instance? Do you have a test area where you could actually load
it and make sure it looks good? Or you could try just loading one item
and see what happens.
-Jose
*From:*Gomez, Joshua [mailto:jngo...@email.gwu.edu] *On Behalf Of
*Joshua Gomez
*Sent:* Tuesday, October 25, 2011 3:41 PM
*To:* Blanco, Jose
*Cc:* dspace-tech@lists.sourceforge.net
*Subject:* Re: [Dspace-tech] bitstream descriptions fail on import
I tried that already. It outputs:
Registering Bitstream:
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia.pdf
Assetstore: 1 Bundle: null Description: null
It is still confusing the description with the bundle
-Josh
On 10/25/2011 02:14 PM, Blanco, Jose wrote:
Josh,
If you have the collection set up to for read anonymous you should not
have to indicate that in the content file, so to keep things simple, I
would try doing this:
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia.pdf
description:Independent_Administrator_Decision
(note that the filename and the description are separated by a tab ).
Try this in the dev area first, just to make sure.
-Jose
*From:*Gomez, Joshua [mailto:jngo...@email.gwu.edu] *On Behalf Of
*Joshua Gomez
*Sent:* Tuesday, October 25, 2011 2:01 PM
*To:* Blanco, Jose
*Cc:* dspace-tech@lists.sourceforge.net
<mailto:dspace-tech@lists.sourceforge.net>
*Subject:* Re: [Dspace-tech] bitstream descriptions fail on import
Jose,
-r means the bitstream is registered rather than actually imported.
The metadata is imported into dspace, but the file itself is not
stored in the directory of dspace's default assetstore. It is stored
in an alternate assetstore.
-s 1 specifies which assetstore the file is located in
-f is the switch for the filename. I think this switch is only
necessary when using those other switches so the script knows when the
filename begins.
I tried going back to my original approach which also specified the
bundle and permissions as described in the manual. The contents files
look like this:
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia.pdf
bundle:ORIGINAL permissions: -r 'Anonymous'
description:Independent_Administrator_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia2.pdf
bundle:ORIGINAL permissions: -r 'Anonymous'
description:Independent_Administrator_Second_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc.pdf
bundle:ORIGINAL permissions: -r 'Anonymous'
description:District_Court_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc2.pdf
bundle:ORIGINAL permissions: -r 'Anonymous'
description:District_Court_Second_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc3.pdf
bundle:ORIGINAL permissions: -r 'Anonymous'
description:District_Court_Third_Decision
When I do it this way the import output has lines like this:
Registering Bitstream:
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia.pdf
Assetstore: 1 Bundle: ORIGINAL Description: ORIGINAL
It is conflating the bundle name and the description text.
When I ran it without the bundle or permissions specified it output
null for the bundle and description. It never distinguished the
description from the bundle.
-Josh
On 10/25/2011 01:29 PM, Blanco, Jose wrote:
Josh,
I'm not familiar with the switches you are using:
-r -s n --f
You put these inside the content file?
-Jose
*From:*Gomez, Joshua [mailto:jngo...@email.gwu.edu] *On Behalf Of
*Joshua Gomez
*Sent:* Tuesday, October 25, 2011 1:25 PM
*To:* Blanco, Jose
*Cc:* dspace-tech@lists.sourceforge.net
<mailto:dspace-tech@lists.sourceforge.net>
*Subject:* Re: [Dspace-tech] bitstream descriptions fail on import
Thank you for your suggestion Jose, but I don't see how it is
significantly different from what I already tried. The only difference
I see is that you may be using underscores instead of spaces in your
descriptions. I tried that, but I still end up with null descriptions
during the import process.
Here is an example contents file from my last attempt:
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia.pdf
description:Independent_Administrator_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_ia2.pdf
description:Independent_Administrator_Second_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc.pdf
description:District_Court_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc2.pdf
description:District_Court_Second_Decision
-r -s 1 -f
gwu_ibt_irb_case_00208/data/PDF/gwu_ibt_irb_case_00208_dc3.pdf
description:District_Court_Third_Decision
Why is it not reading my descriptions?
-Josh
Joshua Gomez
Digital Library Programmer Analyst
George Washington University Libraries
2130 H St, NW Washington, DC 20052
On 10/21/2011 09:54 AM, Blanco, Jose wrote:
Josh,
This is what I do.
I run the import command like this:
./import org.dspace.app.itemimport.ItemImport -a -e admin_id -c
collection_handle -s directory_to_data --m mapfile
And the in the content file you want to make sure you have
File_name\tdescription:The_actual_description
-Jose
*From:*Joshua Gomez [mailto:jngo...@library.gwu.edu]
*Sent:* Thursday, October 20, 2011 8:36 PM
*To:* dspace-tech@lists.sourceforge.net
<mailto:dspace-tech@lists.sourceforge.net>
*Subject:* [Dspace-tech] bitstream descriptions fail on import
When importing items I try to add a description to each bitstream in
the contents file. The manual says to follow this format (I am
registering the items, hence the '-r' at the beginning):
-r -s n -f filepath\tbundle:bundlename\tpermissions: -[r|w] 'group
name'\tdescription: some text
When I use this format the bitstreams don't end up with any
description in the interface. What is strange is that when I watch the
import processing it says:
Registering Bitstream: [filename] Assetstore: 1 Bundle:ORIGINAL
Description:ORIGINAL
Why is it putting ORIGINAL in the description when that is definitely
not what's in the contents file?
I tried doing something different. I used the following format which
skips the bundle and permissions:
-r -s n -f filepath\tdescription: some text
This gave me the following output:
Registering Bitstream: [filename] Assetstore: 1 Bundle:null
Description:null
It seems the import script is only looking at the bundle option.
Anyone understand why this isn't working for me? Is there a bug with
the arguments for the import script or am I missing something?
FYI: I'm using DSpace 1.7 on Ubuntu 10.04, but I noticed this same
problem in DSpace 1.6.
Thanks,
Josh
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
