[Dspace-tech] Exporting metadata from 1.5.2
Hi, We need to export our metadata as a CSV file from a 1.5.2 Dspace version, is there a simple way to do this without having to go through the upgrade steps to a version that supports the export metadata admin task? Regards, Ben -- Dr Ben Ryan Jorum Technical Coordinator (Services) 5.12 Roscoe Building The University of Manchester Oxford Road Manchester M13 9PL Tel: 0160 275 6039 E-mail: benjamin.r...@manchester.ac.ukhttps://outlook.manchester.ac.uk/owa/redir.aspx?C=b28b5bdd1a91425abf8e32748c93f487URL=mailto%3abenjamin.ryan%40manchester.ac.uk -- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Exporting metadata from 1.5.2
On Wed, Aug 8, 2012 at 9:14 AM, Benjamin Ryan benjamin.r...@manchester.ac.uk wrote: We need to export our metadata as a CSV file from a 1.5.2 Dspace version, is there a simple way to do this without having to go through the upgrade steps to a version that supports the “export metadata” admin task? Hi Benjamin, I really think upgrading to 1.6 is the least work. You don't have to do this on your production server if you have a reason not to, you can simply set up a new DSpace 1.6 instance on your PC, then export the items using SIP or, alternatively dump the database and copy the assetstore and run the database_schema_15-16.sql upgrade script on the imported database. In 1.6, you can comfortably se the Batch Metadata Editor [1] to export the CSV. Alternatives I can think of: 1) you might be able to find the BME patch for 1.5, but that's just as much work as upgrading and the results are not guaranteed 2) export in SIP, create a program which will convert the files to CSV 3) search if someone already made an external tool to do 2) 4) construnct some SQL queries that will dump CSV So I really think upgrading is your best option. [1] http://www.dspace.org/1_6_0Documentation/ch08.html#N15FEB Regards, ~~helix84 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Compatibility of DSpace and EPrint OAI-PMH
I have a number of Institution running DSpace. However, our parent institution is running EPrints. Now we intent to harvest metadata from Dspace instances to the EPrint repository. I am wondering if this is possible and if anyone can point me to some documentation. Regards, Admire Mutsikiwa University of Zimbabwe -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Changing Handle URL
Hi, The 123456789 prefix is a bogus, non-existent prefix and the default value if you don't specify your actual handle prefix (assuming you have one). We are not registered with Handle server so we do not have handle prefix that’s the reason we are using 123456789. I came across few handles: http://www.dspace.cam.ac.uk/handle/1810/221922 http://cadair.aber.ac.uk/dspace/handle/2160/1 Does this mean that these universities have registered with Handle server and has 2160 or 1810 registered as institution id? How do we get this institution id generated for us? One more thing to notice in these handles that they do not have 'jspui' in the URL. We got of jspui in the handle url, making it longer. https://qmro.qmul.ac.uk/jspui/handle/123456789/2564 Is there any way to get rid of jspui here, we haven't got xmlui yet? Thanks Kirti -Original Message- From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84 Sent: 07 August 2012 12:44 To: Kirti Bodhmage Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Changing Handle URL Hi Kirti, On Tue, Aug 7, 2012 at 1:27 PM, Kirti Bodhmage k.bodhm...@qmul.ac.uk wrote: I think this question has been asked many times on this list. I believe this is the first time :) My requirement is to change handle url to something smaller. Instead of https://qmro.qmul.ac.uk/jspui/handle/123456789/2564 can we change it to https://qmro.qmul.ac.uk/2564 . The 123456789 prefix is a bogus, non-existent prefix and the default value if you don't specify your actual handle prefix (assuming you have one). As I want to reduce URL to something smaller, is there any way to avoid handle.prefix all together? No, for now, you have to keep it. I tried removing it but didn't work. Although setting it to something like handle.prefix=1 does work. Do not do this. This indicates you're the institution with handle prefix 1, which you surely aren't. Handle redirects would be broken (there's a hdl.handle.net permaling automatically generated with this prefix). SOLUTION: I assume you're running a web server (e.g. Apache HTTPD) in front of your servlet contaniner (e.g. Tomcat). What you want to do is add an URL rewriting module (e.g. mod_rewrite) that will intercept all reqests in form of ^/[1-9]*$ (regex notation) and turn them into redirects to /jspui/handle/123456789/$1. In mod_rewrite notation, this would be: RewriteEngine on RewriteRule ^/[1-9]*$ /jspui/handle/123456789/$1$1 [L] (This is off the top of my head, I didn't test it) I assume any change in handle prefix will be applied to newly submitted records not the existing records in repository. That's right, there's the [dspace]/bin/dspace update-handle-prefix command for updating existing items, but DO NOT change the prefix for the reasons I said above. If I change the handle prefix then the old records will have handle.prefix set to 123456789 and new one handle.prefix = 1. Is there any problem having both handle in repository? We have Symplectic Elements and repository tools depositing records into Dspace. Will changing the handle url create any issue with publications?( a question for Symplectic) Like I said above, don't change the handle prefix. Regards, ~~helix84 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Searching : Diacritics Indexing
Hi all, We are running a bilingual (French/English) instance of last version of Dspace (1.8.2). We have some problems with the search with diacritics. The Dspace's searcher doesn't find words with accented characters when the search doesn't include these accents. We modified (\dspace-1.8.2-src-release\dspace-api\src\main\java\org\dspace\search\DSAnalyzer.java) and we added the followings two lines: ISOLatin1AccentFilter; result = new ISOLatin1AccentFilter(result); Rebuild, Re-index Dspace But the problem was not resolved. If anyone has solved this problem - Please Help!!! Thank You Regards, -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Searching : Diacritics Indexing
Hi, I think the problem may lie in the first line. It should be import org.apache.lucene.analysis.ISOLatin1AccentFilter; and be included at the top of the file with the rest of the imports. The second line looks fine, and goes with the rest of the filter statements. B-- On 8/8/2012 at 12:14 PM, in message 85c980bb1085994793231c3abd13a5629ee...@xmbx03.sti.usherbrooke.ca, Hatem Jlassi hatem.jla...@usherbrooke.ca wrote: Hi all, We are running a bilingual (French/English) instance of last version of Dspace (1.8.2). We have some problems with the search with diacritics. The Dspace's searcher doesn't find words with accented characters when the search doesn't include these accents. We modified (\dspace-1.8.2-src-release\dspace-api\src\main\java\org\dspace\search \DSAnalyzer.java) and we added the followings two lines: ISOLatin1AccentFilter; result = new ISOLatin1AccentFilter(result); Rebuild, Re-index Dspace But the problem was not resolved. If anyone has solved this problem - Please Help!!! Thank You Regards, -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Searching : Diacritics Indexing
Hi,
Thanks for your response.,
But, the source code is correct, following the file content.
Regards,
/**
* The contents of this file are subject to the license and copyright
* detailed in the LICENSE and NOTICE files at the root of the source
* tree and available online at
*
* http://www.dspace.org/license/
*/
package org.dspace.search;
import java.io.Reader;
import java.util.Set;
import org.apache.lucene.analysis.Analyzer;
import org.apache.lucene.analysis.ISOLatin1AccentFilter;
import org.apache.lucene.analysis.LowerCaseFilter;
import org.apache.lucene.analysis.PorterStemFilter;
import org.apache.lucene.analysis.StopFilter;
import org.apache.lucene.analysis.StopwordAnalyzerBase;
import org.apache.lucene.analysis.Tokenizer;
import org.apache.lucene.analysis.TokenStream;
import org.apache.lucene.analysis.standard.StandardFilter;
import org.apache.lucene.util.Version;
import org.dspace.core.ConfigurationManager;
/**
* Custom Lucene Analyzer that combines the standard filter, lowercase filter,
* stemming and stopword filters.
*/
public class DSAnalyzer extends StopwordAnalyzerBase
{
protected final Version matchVersion;
/*
* An array containing some common words that are not usually useful for
* searching.
*/
protected static final String[] STOP_WORDS =
{
// new stopwords (per MargretB)
a, am, and, are, as, at, be, but, by, for,
if, in, into, is, it, no, not, of, on, or,
the, to, was
// old stopwords (Lucene default)
/*
* a, and, are, as, at, be, but, by, for, if, in,
* into, is, it, no, not, of, on, or, s, such, t,
* that, the, their,then, there,these, they, this, to,
* was, will, with
*/
};
/*
* Stop table
*/
protected final Set stopSet;
/**
* Builds an analyzer
* @param matchVersion Lucene version to match
*/
public DSAnalyzer(Version matchVersion) {
super(matchVersion, StopFilter.makeStopSet(matchVersion, STOP_WORDS));
this.stopSet = StopFilter.makeStopSet(matchVersion, STOP_WORDS);
this.matchVersion = matchVersion;
}
@Override
protected TokenStreamComponents createComponents(String fieldName, Reader
reader) {
final Tokenizer source = new DSTokenizer(matchVersion, reader);
TokenStream result = new StandardFilter(matchVersion, source);
result = new StandardFilter(result);
result = new LowerCaseFilter(matchVersion, result);
result = new StopFilter(matchVersion, result, stopSet);
result = new PorterStemFilter(result);
result = new ISOLatin1AccentFilter(result);
return new TokenStreamComponents(source, result);
return result;
}
@Override
public int getPositionIncrementGap(String fieldName)
{
// If it is the default field, or bounded fields is turned off in the
config, return the default value
if (default.equalsIgnoreCase(fieldName) ||
!ConfigurationManager.getBooleanProperty(search.boundedfields, false))
{
return super.getPositionIncrementGap(fieldName);
}
// Not the default field, and we want bounded fields, so return an
large gap increment
return 10;
}
}
-Message d'origine-
De : Brian Freels-Stendel [mailto:bfre...@unm.edu]
Envoyé : 8 août 2012 14:41
À : DSpace-tech@lists.sourceforge.net; Hatem Jlassi
Objet : Re: [Dspace-tech] Searching : Diacritics Indexing
Hi,
I think the problem may lie in the first line. It should be
import org.apache.lucene.analysis.ISOLatin1AccentFilter;
and be included at the top of the file with the rest of the imports. The
second line looks fine, and goes with the rest of the filter statements.
B--
On 8/8/2012 at 12:14 PM, in message
85c980bb1085994793231c3abd13a5629ee...@xmbx03.sti.usherbrooke.ca, Hatem
Jlassi hatem.jla...@usherbrooke.ca wrote:
Hi all,
We are running a bilingual (French/English) instance of last version
of Dspace (1.8.2). We have some problems with the search with
diacritics. The Dspace's searcher doesn't find words with accented
characters when the search doesn't include these accents.
We modified
(\dspace-1.8.2-src-release\dspace-api\src\main\java\org\dspace\search
\DSAnalyzer.java) and we added the followings two lines:
ISOLatin1AccentFilter;
result = new ISOLatin1AccentFilter(result); Rebuild, Re-index Dspace
But the problem was not resolved.
If anyone has solved this problem - Please Help!!! Thank You
Regards,
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
