Re: [Dspace-tech] Reset handles
Thanks, Claudia. I was already using the prefix assigned by CNRI, and wanted delete all of the handles created during testing. After dropping the database and redeploying a fresh install, I see that the handles have reset themselves -- which is what I wanted to do. I love problems that solve themselves. Eric On Wed, Jan 21, 2009 at 11:22 AM, Claudia Jürgen wrote: > Hi Eric, > > there is the [dspace]/bin/update-handle-script which allows you to change > the handle prefix e.g. from 12345689 in a test instance to the handle > assigned to you be CNRI. > > Hope that helps > > Claudia Jürgen > > > Eric Luhrs schrieb: >> >> After several months of testing, we're soon planning to launch DSpace >> to our campus. Before doing so, I plan to drop and re-create the >> database, and I wonder if there is an equivalent step for handles. Is >> it possible to reset them? Has anyone done so? I'd also like to know >> if re-setting them is inadvisable for any reason. >> >> Thanks in advance, >> >> Eric Luhrs >> Lafayette College >> >> >> -- >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> ___ >> DSpace-tech mailing list >> DSpace-tech@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-tech > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] handle server
Hi all I've got the database and asset store migrated from our machine running 1.4 across to the new 1.5 instance.. I'm now looking at configuring the handle server, and I just have a few questions about it: If I run $DSpace/bin/dsrun net.handle.server.SimpleSetup $DSpace/handle-server/ and send the generated sitebndl.zip to handle.net and get a new prefix will the handles for the items I've migrated to the new system still be valid? The new system will eventually have the same dns hostname as the old one, but not the same ip address. Is it possible just to copy the contents of the handle-server directory from the old install to the new one? If not will I get a new handle (so all the items imported will have one handle and any new items added will have a different one) and does that mean we have to pay the registration (referred to at http://www.handle.net/service_agreement.html) twice? Thanks. Rod -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions
Thanks for all your help Tim! I think this will help us out a lot! Best, Sue -Original Message- From: Tim Donohue [mailto:tdono...@illinois.edu] Sent: Wednesday, January 21, 2009 4:54 PM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Cc: Diggory Mark; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions Sue, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: > Hi Tim, > Thanks to all for the suggestions. Basically I am trying to > prevent filter-media from attempting to filter our .pdf files and I want > index-all to index only our .txt files. > > So if I remove the pdffilter parameters from dspace.cfg and I have > all our .txt files in the TEXT bundle (using one of the 3 options you > outlined), this should work and we shouldn't have to run filter-media at > all, right? That's almost correct, except for the last part of your statement. You'll notice that in the options I laid out below, Options #1 and #3 specifically state you STILL need to run 'filter-media'. This is because in both those options you are starting with the *.txt files in the ORIGINAL bundle, and they need to be copied to the TEXT bundle before they can be indexed. Is this starting to make some sense? Filter-media is what does extraction of full text (from PDF, HTML, Word or Plain text formats) and generates a corresponding *.txt file in the TEXT bundle containing the extracted full text. Since the 'index-all' script will ONLY index *.txt from the TEXT bundle, you will always need to run 'filter-media' first unless you've manually added *.txt to the TEXT bundle. - Tim > > Thanks again, > Sue > > -Original Message- > From: Tim Donohue [mailto:tdono...@illinois.edu] > Sent: Wednesday, January 21, 2009 10:54 AM > To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] > Cc: Diggory Mark; dspace-tech@lists.sourceforge.net; Kimbrough, Glenn W. > (LARC-B7)[NCI INFORMATION SYSTEMS]; Warren, Douglas Lewis (LARC-B7)[NCI > INFORMATION SYSTEMS]; Smail, James W. (LARC-B702)[NCI INFORMATION > SYSTEMS] > Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions > > Sue, > > Sorry, we've all been talking across each other a bit. As you can > probably tell, there's really no "correct" answer on how to do this, > rather there's a variety of options to choose from > > Essentially, you have 3 options that have been laid out by Mark, Claudia > > and myself. I'm not certain which will be *easiest* off the top of my > head: > > [Option 1] Add the *.txt files to the "ORIGINAL" bundle (which is where > > they are added by default). If they are in the "ORIGINAL" bundle you > will have to run 'filter-media' to "filter" them into the "TEXT" bundle. > >Then, you will run 'index-all' to index them for searching (as noted > 'index-all' only indexes documents in the "TEXT" bundle). You will also > > need to modify the UI if you don't want these *.txt files to be visible > to normal users. > > [Option 2] Add the *.txt files to the "TEXT" bundle directly. There is > > no way to do this via normal DSpace user interfaces. You can however do > > this during the normal command-line bulk item import process by > specifying a "bundle" name in the 'contents' file. See the DSpace Docs > for more information on this: > http://dspace.svn.sourceforge.net/viewvc/dspace/trunk/dspace/docs/applic > ation.html#itemimporter > > [Option 3] Claudia's suggestion is very similar to Option #1. However, > > as she notes and easy way to "hide" the *.txt files from the UI is to go > > into the DSpace Administration UI (specifically the "Bitstream Format > Registry" and mark the *.txt format as "internal"). This tells DSpace > that ALL *.txt files should be considered internal files, and should > NEVER be displayed in the UI. So, you'd only want to do this if you > never want any *.txt files to be displayed from the UI. > > > In my opinion (others may have differing opinions), it'd be safer & > potentially easier to go with either option #1 or #3. The danger of > option #2 is that the "TEXT" bundle tends to be managed by the > "filter-media" script in DSpace. As long as you are always aware that > you manually added files to this bundle, you should be fine. But, if > you ever ran 'filter-media' in "force" mode (with the -f option), > there'd be a possibility the 'filter-media' script would overwrite all > your manually added *.txt files in that bundle. > > Hopefully that gives you a decent lay of the land. There may be yet > other options out there, but at least this gives you a few to work off > of. > > - Tim > > > > Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: >> I did the following query against the bundle table and it seems we > only >> have 3 bundle "name"s in the table: LICENSE, ORIGINAL, & TEXT: >> >> */select count(*)/* >> >> */ , name /* >> >> */ from bundle
Re: [Dspace-tech] Modifying values exposed via OAI unqualified DC
OK, got it, thanks very much, Mark - "Stuart Lewis [sdl]" wrote: > Hi Mark, > > > Claudia, > > Thanks for the pointer, but can you tell me where this file should > > be? I've done a find on my server and it's not coming up. > > Mark > > DSpace 1.5.x: > > [dspace-src]/dspace-oai/dspace-oai-api/src/main/java/org/dspace/app/oai/OAID > CCrosswalk.java > > DSpace 1.4.x and earlier: > > [dspace-src]/src/org/dspace/app/oai/OAIDCCrosswalk.java > > Thanks, > > > Stuart > _ > > Gwasanaethau Gwybodaeth Information Services > Prifysgol Aberystwyth Aberystwyth University > > E-bost / E-mail: stuart.le...@aber.ac.uk > Ffon / Tel: (01970) 622860 > _ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Modifying values exposed via OAI unqualified DC
[I've done a find [on dc.identifier] on my server and it's not coming up] Hi, cd [path to dspace] ; find . -type f -print0 |xargs -0 fgrep -i dc.identifier I got some results with the above command. -- Van Ly : UNIX System Administrator : University of Sydney Library : e= v...@usyd.edu.au : t= +61 2 9351 4304 -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions
Sue, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: > Hi Tim, > Thanks to all for the suggestions. Basically I am trying to > prevent filter-media from attempting to filter our .pdf files and I want > index-all to index only our .txt files. > > So if I remove the pdffilter parameters from dspace.cfg and I have > all our .txt files in the TEXT bundle (using one of the 3 options you > outlined), this should work and we shouldn't have to run filter-media at > all, right? That's almost correct, except for the last part of your statement. You'll notice that in the options I laid out below, Options #1 and #3 specifically state you STILL need to run 'filter-media'. This is because in both those options you are starting with the *.txt files in the ORIGINAL bundle, and they need to be copied to the TEXT bundle before they can be indexed. Is this starting to make some sense? Filter-media is what does extraction of full text (from PDF, HTML, Word or Plain text formats) and generates a corresponding *.txt file in the TEXT bundle containing the extracted full text. Since the 'index-all' script will ONLY index *.txt from the TEXT bundle, you will always need to run 'filter-media' first unless you've manually added *.txt to the TEXT bundle. - Tim > > Thanks again, > Sue > > -Original Message- > From: Tim Donohue [mailto:tdono...@illinois.edu] > Sent: Wednesday, January 21, 2009 10:54 AM > To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] > Cc: Diggory Mark; dspace-tech@lists.sourceforge.net; Kimbrough, Glenn W. > (LARC-B7)[NCI INFORMATION SYSTEMS]; Warren, Douglas Lewis (LARC-B7)[NCI > INFORMATION SYSTEMS]; Smail, James W. (LARC-B702)[NCI INFORMATION > SYSTEMS] > Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions > > Sue, > > Sorry, we've all been talking across each other a bit. As you can > probably tell, there's really no "correct" answer on how to do this, > rather there's a variety of options to choose from > > Essentially, you have 3 options that have been laid out by Mark, Claudia > > and myself. I'm not certain which will be *easiest* off the top of my > head: > > [Option 1] Add the *.txt files to the "ORIGINAL" bundle (which is where > > they are added by default). If they are in the "ORIGINAL" bundle you > will have to run 'filter-media' to "filter" them into the "TEXT" bundle. > >Then, you will run 'index-all' to index them for searching (as noted > 'index-all' only indexes documents in the "TEXT" bundle). You will also > > need to modify the UI if you don't want these *.txt files to be visible > to normal users. > > [Option 2] Add the *.txt files to the "TEXT" bundle directly. There is > > no way to do this via normal DSpace user interfaces. You can however do > > this during the normal command-line bulk item import process by > specifying a "bundle" name in the 'contents' file. See the DSpace Docs > for more information on this: > http://dspace.svn.sourceforge.net/viewvc/dspace/trunk/dspace/docs/applic > ation.html#itemimporter > > [Option 3] Claudia's suggestion is very similar to Option #1. However, > > as she notes and easy way to "hide" the *.txt files from the UI is to go > > into the DSpace Administration UI (specifically the "Bitstream Format > Registry" and mark the *.txt format as "internal"). This tells DSpace > that ALL *.txt files should be considered internal files, and should > NEVER be displayed in the UI. So, you'd only want to do this if you > never want any *.txt files to be displayed from the UI. > > > In my opinion (others may have differing opinions), it'd be safer & > potentially easier to go with either option #1 or #3. The danger of > option #2 is that the "TEXT" bundle tends to be managed by the > "filter-media" script in DSpace. As long as you are always aware that > you manually added files to this bundle, you should be fine. But, if > you ever ran 'filter-media' in "force" mode (with the -f option), > there'd be a possibility the 'filter-media' script would overwrite all > your manually added *.txt files in that bundle. > > Hopefully that gives you a decent lay of the land. There may be yet > other options out there, but at least this gives you a few to work off > of. > > - Tim > > > > Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: >> I did the following query against the bundle table and it seems we > only >> have 3 bundle "name"s in the table: LICENSE, ORIGINAL, & TEXT: >> >> */select count(*)/* >> >> */ , name /* >> >> */ from bundle /* >> >> */ group by 2 /* >> >> */ order by 2/* >> >> */ /* >> >> All the .txt files we created in our 1000 document test are in the >> ORIGINAL bundle, according to NAME in the bundle table. So if I run >> this query and then run index-all, these .txt files should be >> searchable, correct? >> >> */UPDATE bundle/* >> >> */ SET name = 'TEXT'/* >> >> */ WHERE bundle_id
Re: [Dspace-tech] Modifying values exposed via OAI unqualified DC
Hi Mark, > Claudia, Thanks for the pointer, but can you tell me where this file should > be? I've done a find on my server and it's not coming up. Mark DSpace 1.5.x: [dspace-src]/dspace-oai/dspace-oai-api/src/main/java/org/dspace/app/oai/OAID CCrosswalk.java DSpace 1.4.x and earlier: [dspace-src]/src/org/dspace/app/oai/OAIDCCrosswalk.java Thanks, Stuart _ Gwasanaethau Gwybodaeth Information Services Prifysgol Aberystwyth Aberystwyth University E-bost / E-mail: stuart.le...@aber.ac.uk Ffon / Tel: (01970) 622860 _ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions
Hi Tim, Thanks to all for the suggestions. Basically I am trying to prevent filter-media from attempting to filter our .pdf files and I want index-all to index only our .txt files. So if I remove the pdffilter parameters from dspace.cfg and I have all our .txt files in the TEXT bundle (using one of the 3 options you outlined), this should work and we shouldn't have to run filter-media at all, right? Thanks again, Sue -Original Message- From: Tim Donohue [mailto:tdono...@illinois.edu] Sent: Wednesday, January 21, 2009 10:54 AM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Cc: Diggory Mark; dspace-tech@lists.sourceforge.net; Kimbrough, Glenn W. (LARC-B7)[NCI INFORMATION SYSTEMS]; Warren, Douglas Lewis (LARC-B7)[NCI INFORMATION SYSTEMS]; Smail, James W. (LARC-B702)[NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions Sue, Sorry, we've all been talking across each other a bit. As you can probably tell, there's really no "correct" answer on how to do this, rather there's a variety of options to choose from Essentially, you have 3 options that have been laid out by Mark, Claudia and myself. I'm not certain which will be *easiest* off the top of my head: [Option 1] Add the *.txt files to the "ORIGINAL" bundle (which is where they are added by default). If they are in the "ORIGINAL" bundle you will have to run 'filter-media' to "filter" them into the "TEXT" bundle. Then, you will run 'index-all' to index them for searching (as noted 'index-all' only indexes documents in the "TEXT" bundle). You will also need to modify the UI if you don't want these *.txt files to be visible to normal users. [Option 2] Add the *.txt files to the "TEXT" bundle directly. There is no way to do this via normal DSpace user interfaces. You can however do this during the normal command-line bulk item import process by specifying a "bundle" name in the 'contents' file. See the DSpace Docs for more information on this: http://dspace.svn.sourceforge.net/viewvc/dspace/trunk/dspace/docs/applic ation.html#itemimporter [Option 3] Claudia's suggestion is very similar to Option #1. However, as she notes and easy way to "hide" the *.txt files from the UI is to go into the DSpace Administration UI (specifically the "Bitstream Format Registry" and mark the *.txt format as "internal"). This tells DSpace that ALL *.txt files should be considered internal files, and should NEVER be displayed in the UI. So, you'd only want to do this if you never want any *.txt files to be displayed from the UI. In my opinion (others may have differing opinions), it'd be safer & potentially easier to go with either option #1 or #3. The danger of option #2 is that the "TEXT" bundle tends to be managed by the "filter-media" script in DSpace. As long as you are always aware that you manually added files to this bundle, you should be fine. But, if you ever ran 'filter-media' in "force" mode (with the -f option), there'd be a possibility the 'filter-media' script would overwrite all your manually added *.txt files in that bundle. Hopefully that gives you a decent lay of the land. There may be yet other options out there, but at least this gives you a few to work off of. - Tim Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: > I did the following query against the bundle table and it seems we only > have 3 bundle "name"s in the table: LICENSE, ORIGINAL, & TEXT: > > */select count(*)/* > > */ , name /* > > */ from bundle /* > > */ group by 2 /* > > */ order by 2/* > > */ /* > > All the .txt files we created in our 1000 document test are in the > ORIGINAL bundle, according to NAME in the bundle table. So if I run > this query and then run index-all, these .txt files should be > searchable, correct? > > */UPDATE bundle/* > > */ SET name = 'TEXT'/* > > */ WHERE bundle_id = /* > > */ (SELECT bu.bundle_id /* > > */ FROM bitstream bi/* > > */, bundle2bitstream b2b/* > > */, bundlebu/* > > */ WHERE bi.bitstream_id = b2b.bitstream_id/* > > */ AND b2b.bundle_id = bu.bundle_id/* > > */ AND bundle.bundle_id = bu.bundle_id/* > > */ AND bu.name = 'ORIGINAL'/* > > */ AND bi.name LIKE '%.txt') /* > > > > Let me know what you think. > > Thanks again, > > Sue > > > > > > -Original Message- > From: Tim Donohue [mailto:tdono...@illinois.edu] > Sent: Tuesday, January 20, 2009 2:12 PM > To: Diggory Mark > Cc: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS]; > dspace-tech@lists.sourceforge.net; Kimbrough, Glenn W. (LARC-B7)[NCI > INFORMATION SYSTEMS]; Warren, Douglas Lewis (LARC-B7)[NCI INFORMATION > SYSTEMS]; Smail, James W. (LARC-B702)[NCI INFORMATION SYSTEMS] > Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions > > > > Mark, > > > > That's correct, that the in
Re: [Dspace-tech] Modifying values exposed via OAI unqualified DC
Claudia, Thanks for the pointer, but can you tell me where this file should be? I've done a find on my server and it's not coming up. Mark Mark Jordan Head of Library Systems W.A.C. Bennett Library, Simon Fraser University Burnaby, British Columbia, V5A 1S6, Canada Voice: 778.782.5753 / Fax: 778.782.3023 mjor...@sfu.ca - "Claudia Juergen" wrote: > Hi Mark, > > take a look at > org.dspace.app.oai.OAIDCCrosswalk > > Hope that helps > > Claudia Jürgen > > > Hi, > > > > I'm sure this is documented somewhere but I've had no luck finding > it. > > > > We want to modify the value exposed in unqualified DC OAI output, > > specifically, we'd like the dc.identifier element to use local > handle URLS > > like http://ir.lib.sfu.ca/handle/1892/70 instead of the equivalent > > http://hdl.handle.net URLs. > > > > I looked in the crosswalks directory expecting to find a file for > uDC but > > there wasn't one there. If anyone has done anything like this I'd be > very > > grateful to hear about it. > > > > Mark > > > > Mark Jordan > > Head of Library Systems > > W.A.C. Bennett Library, Simon Fraser University > > Burnaby, British Columbia, V5A 1S6, Canada > > Voice: 778.782.5753 / Fax: 778.782.3023 > > mjor...@sfu.ca > > > > > -- > > This SF.net email is sponsored by: > > SourcForge Community > > SourceForge wants to tell your story. > > http://p.sf.net/sfu/sf-spreadtheword > > ___ > > DSpace-tech mailing list > > DSpace-tech@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Modifying values exposed via OAI unqualified DC
Hi Mark, take a look at org.dspace.app.oai.OAIDCCrosswalk Hope that helps Claudia Jürgen > Hi, > > I'm sure this is documented somewhere but I've had no luck finding it. > > We want to modify the value exposed in unqualified DC OAI output, > specifically, we'd like the dc.identifier element to use local handle URLS > like http://ir.lib.sfu.ca/handle/1892/70 instead of the equivalent > http://hdl.handle.net URLs. > > I looked in the crosswalks directory expecting to find a file for uDC but > there wasn't one there. If anyone has done anything like this I'd be very > grateful to hear about it. > > Mark > > Mark Jordan > Head of Library Systems > W.A.C. Bennett Library, Simon Fraser University > Burnaby, British Columbia, V5A 1S6, Canada > Voice: 778.782.5753 / Fax: 778.782.3023 > mjor...@sfu.ca > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Modifying values exposed via OAI unqualified DC
Hi, I'm sure this is documented somewhere but I've had no luck finding it. We want to modify the value exposed in unqualified DC OAI output, specifically, we'd like the dc.identifier element to use local handle URLS like http://ir.lib.sfu.ca/handle/1892/70 instead of the equivalent http://hdl.handle.net URLs. I looked in the crosswalks directory expecting to find a file for uDC but there wasn't one there. If anyone has done anything like this I'd be very grateful to hear about it. Mark Mark Jordan Head of Library Systems W.A.C. Bennett Library, Simon Fraser University Burnaby, British Columbia, V5A 1S6, Canada Voice: 778.782.5753 / Fax: 778.782.3023 mjor...@sfu.ca -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Reset handles
Hi Eric, there is the [dspace]/bin/update-handle-script which allows you to change the handle prefix e.g. from 12345689 in a test instance to the handle assigned to you be CNRI. Hope that helps Claudia Jürgen Eric Luhrs schrieb: > After several months of testing, we're soon planning to launch DSpace > to our campus. Before doing so, I plan to drop and re-create the > database, and I wonder if there is an equivalent step for handles. Is > it possible to reset them? Has anyone done so? I'd also like to know > if re-setting them is inadvisable for any reason. > > Thanks in advance, > > Eric Luhrs > Lafayette College > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Reset handles
After several months of testing, we're soon planning to launch DSpace to our campus. Before doing so, I plan to drop and re-create the database, and I wonder if there is an equivalent step for handles. Is it possible to reset them? Has anyone done so? I'd also like to know if re-setting them is inadvisable for any reason. Thanks in advance, Eric Luhrs Lafayette College -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions
Sue, Sorry, we've all been talking across each other a bit. As you can probably tell, there's really no "correct" answer on how to do this, rather there's a variety of options to choose from Essentially, you have 3 options that have been laid out by Mark, Claudia and myself. I'm not certain which will be *easiest* off the top of my head: [Option 1] Add the *.txt files to the "ORIGINAL" bundle (which is where they are added by default). If they are in the "ORIGINAL" bundle you will have to run 'filter-media' to "filter" them into the "TEXT" bundle. Then, you will run 'index-all' to index them for searching (as noted 'index-all' only indexes documents in the "TEXT" bundle). You will also need to modify the UI if you don't want these *.txt files to be visible to normal users. [Option 2] Add the *.txt files to the "TEXT" bundle directly. There is no way to do this via normal DSpace user interfaces. You can however do this during the normal command-line bulk item import process by specifying a "bundle" name in the 'contents' file. See the DSpace Docs for more information on this: http://dspace.svn.sourceforge.net/viewvc/dspace/trunk/dspace/docs/application.html#itemimporter [Option 3] Claudia's suggestion is very similar to Option #1. However, as she notes and easy way to "hide" the *.txt files from the UI is to go into the DSpace Administration UI (specifically the "Bitstream Format Registry" and mark the *.txt format as "internal"). This tells DSpace that ALL *.txt files should be considered internal files, and should NEVER be displayed in the UI. So, you'd only want to do this if you never want any *.txt files to be displayed from the UI. In my opinion (others may have differing opinions), it'd be safer & potentially easier to go with either option #1 or #3. The danger of option #2 is that the "TEXT" bundle tends to be managed by the "filter-media" script in DSpace. As long as you are always aware that you manually added files to this bundle, you should be fine. But, if you ever ran 'filter-media' in "force" mode (with the -f option), there'd be a possibility the 'filter-media' script would overwrite all your manually added *.txt files in that bundle. Hopefully that gives you a decent lay of the land. There may be yet other options out there, but at least this gives you a few to work off of. - Tim Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: > I did the following query against the bundle table and it seems we only > have 3 bundle "name"s in the table: LICENSE, ORIGINAL, & TEXT: > > */select count(*)/* > > */ , name /* > > */ from bundle /* > > */ group by 2 /* > > */ order by 2/* > > */ /* > > All the .txt files we created in our 1000 document test are in the > ORIGINAL bundle, according to NAME in the bundle table. So if I run > this query and then run index-all, these .txt files should be > searchable, correct? > > */UPDATE bundle/* > > */ SET name = 'TEXT'/* > > */ WHERE bundle_id = /* > > */ (SELECT bu.bundle_id /* > > */ FROM bitstream bi/* > > */, bundle2bitstream b2b/* > > */, bundlebu/* > > */ WHERE bi.bitstream_id = b2b.bitstream_id/* > > */ AND b2b.bundle_id = bu.bundle_id/* > > */ AND bundle.bundle_id = bu.bundle_id/* > > */ AND bu.name = 'ORIGINAL'/* > > */ AND bi.name LIKE '%.txt') /* > > > > Let me know what you think. > > Thanks again, > > Sue > > > > > > -Original Message- > From: Tim Donohue [mailto:tdono...@illinois.edu] > Sent: Tuesday, January 20, 2009 2:12 PM > To: Diggory Mark > Cc: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS]; > dspace-tech@lists.sourceforge.net; Kimbrough, Glenn W. (LARC-B7)[NCI > INFORMATION SYSTEMS]; Warren, Douglas Lewis (LARC-B7)[NCI INFORMATION > SYSTEMS]; Smail, James W. (LARC-B702)[NCI INFORMATION SYSTEMS] > Subject: Re: [Dspace-tech] DSpace 1.4.2 / 1.5.x filter-media questions > > > > Mark, > > > > That's correct, that the indexer only indexes files in the TEXT bundle. > > But, that's why I had recommended to Susan to first run 'filter-media' > > script. The 'filter-media' script will take text files in the CONTENT > > bundle and essentially copy them over to the TEXT bundle for indexing. > > > > So, you are correct that the *.txt files could be immediately put in the > > TEXT bundle (which would also avoid them being exposed publicly). But, > > the alternative would be to put the *.txt files in the CONTENT bundle > > and run 'filter-media' to "filter" it into the TEXT bundle. (However, as > > you noted, this latter option would require UI alteration to hide the > > *.txt files, if they shouldn't be accessible). > > > > - Tim > > > > Diggory Mark wrote: > >> Actually... > >> > >> Looking at the code of DSIndexer... I'm sure, written by among others... > >> myself. We find that only B
Re: [Dspace-tech] Modify Display - Manakin
Here is a nice tutorial you might try. It is more DSpace 1.5 centric and talks about how to do overlays. http://pubs.or08.ecs.soton.ac.uk/135/ Mark On Jan 20, 2009, at 11:28 PM, Lyn Amery wrote: I’m having no luck with modifying the default display for items (search results, browsing results, etc) using Manakin/xmlui. I’ve been following the How-To Guide, but it’s for DSpace 1.4.2/Manakin 1.1 and I’ve installed DSpace 1.5.1. Much of the document is obviously out of date. Even the 1.5.1 manual seems to be behind. It often refers to directories and executables which don’t exist. I’ve searched for more recent versions and have made endless searches of dspace.org and the wiki, but I’m getting nowhere. It looks like these sorts of changes really shouldn’t be that hard to do. Is there a stash of updated documentation somewhere that I have missed? Cheers, Lyn Lyn Amery Web Analyst/Programmer State Records Office (08) 9427 3493 lyn.am...@sro.wa.gov.au -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech ~ Mark R. Diggory http://purl.org/net/mdiggory/homepage -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
