[Dspace-tech] Basic Installation Error
Hi I am getting the following error when trying to install DSpace. ++ [EMAIL PROTECTED] dspace-1.4.2-source]# ant fresh_install Buildfile: build.xml BUILD FAILED /tmp/dspace-1.4.2-source/build.xml:88: No supported regular expression matcher found Total time: 0 seconds [EMAIL PROTECTED] dspace-1.4.2-source]# ++ Server Specs Linux 2.6.8.1-12mdksmp #1 SMP Fri Oct 1 11:24:45 CEST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz unknown GNU/Linux Java version Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) Ant Version Apache Ant version 1.6.5 compiled on November 27 2006 PostgresSQL Version postgres (PostgreSQL) 7.3.2 Tomcat Version Apache Tomcat/4.1.31 Apache Version Apache version 2.0.50 Please help. Thanks Derek -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to [EMAIL PROTECTED] This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Persistent identifiers in DSpace -- thoughtsplease
On Tue, 2007-05-29 at 14:58 +0100, James Rutherford wrote: Using UUIDs (as suggested earlier) would *work*, but would produce horrid URLs. Note that I never suggested using UUIDs as part of a URL. What I said is that UUIDs would give you a robust scheme of internal unique identifiers - and in having that, the use of all other identifier schemes are reduced simply to a matter of how you map to/from the UUIDs. We could easily have an out-of-the-box mapping scheme to non-persistent 'friendly' identifiers if the concern is simply to have cleaner URLs. But even if UUIDs where exposed in the URLs (in a default installation), is that necessarily a problem? The ugliness of it would at least encourage people to think about the issues of id persistence / assignment in relation to that repository. By assigning UUIDs as the primary / internal id of all persistent objects in DSpace, we can use tried and tested, well understood algorithms to generate IDs that are virtually guaranteed to be unique, which would open up potential usage / installation scenarios that could otherwise be impractical. It would also have some consistency with the JCR specification, and you've got the potential to make them public, persistent identifiers if that is deemed suitable for a given installation. G This email has been scanned by Postini. For more information please visit http://www.postini.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Postgresql datase issues--resolved
I am happy to report that your assistance out there in DSpace-land has helped me resolve the restoration of a database issue. I am now ready to upgrade our PostgreSQL to newer versions. Any one using the most recent? Has there been any compatability issues with DSpace? TIA Jeffrey A. Trimble Systems Librarian Youngstown State University Youngstown, OH [EMAIL PROTECTED] (330) 941-2483 http://digital.maag.ysu.edu http://www.maag.ysu.edu http://jupiter.ysu.edu - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Upgrading from mod_webapp to mod_jk (update)
My thanks to Brad Teal at the University and Minnesota and Josef Bicik at the University of Exeter. I have my apache/mod_jk/tomcat/dspace setup working properly now. You think after 30 years of programming, I would know better, but I was surprised at how tricky the whole thing was. *** George Kozak Coordinator Web Development and Management Digital Media Group 501 Olin Library Cornell University 607-255-8924 *** [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] DSpace with Oracle 10 Installation Problem.
Hi, I'm currently trying to install the Dspace 1.4.2 with oracle support on a Red Hat machine. My Oracle Server is on another machine. I've been trying several times to use the Installation method provided with the source, And even thoug the ojdbc14.jar is in place, I'm constantly getting the following error in the setup_database part of the fresh install_process setup_database: [java] 2007-05-30 09:03:14,928 INFO org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2007-05-30 09:03:15,037 INFO org.dspace.core.ConfigurationManager @ DSpace logging installed using log4j.properties [java] 2007-05-30 09:03:15,125 FATAL org.dspace.storage.rdbms.InitializeDatabase @ Caught exception: [java] java.sql.SQLException: No suitable driver [java] at java.sql.DriverManager.getConnection(DriverManager.java:545) [java] at java.sql.DriverManager.getConnection(DriverManager.java:171) [java] at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(Driv erManagerConnectionFactory.java:48) [java] at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnect ionFactory.java:290) [java] at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPoo l.java:840) [java] at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175) [java] at java.sql.DriverManager.getConnection(DriverManager.java:525) [java] at java.sql.DriverManager.getConnection(DriverManager.java:193) [java] at org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java: 717) [java] at org.dspace.storage.rdbms.DatabaseManager.loadSql(DatabaseManager.java:1062) [java] at org.dspace.storage.rdbms.InitializeDatabase.main(InitializeDatabase.java:71) Anyone have an idea? Stéphane Collin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace with Oracle 10 Installation Problem.
I had a similar problem. The fix for me was to format the db.url like this: db.url = jdbc:oracle:thin:@//host:port/dspace as opposed to the Install doc which lists: db.url = jdbc.oracle.thin:@//host:port/dspace -Greg Stéphane Collin wrote: Hi, I'm currently trying to install the Dspace 1.4.2 with oracle support on a Red Hat machine. My Oracle Server is on another machine. I've been trying several times to use the Installation method provided with the source, And even thoug the ojdbc14.jar is in place, I'm constantly getting the following error in the setup_database part of the fresh install_process setup_database: [java] 2007-05-30 09:03:14,928 INFO org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database [java] 2007-05-30 09:03:15,037 INFO org.dspace.core.ConfigurationManager @ DSpace logging installed using log4j.properties [java] 2007-05-30 09:03:15,125 FATAL org.dspace.storage.rdbms.InitializeDatabase @ Caught exception: [java] java.sql.SQLException: No suitable driver [java] at java.sql.DriverManager.getConnection(DriverManager.java:545) [java] at java.sql.DriverManager.getConnection(DriverManager.java:171) [java] at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48) [java] at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) [java] at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:840) [java] at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175) [java] at java.sql.DriverManager.getConnection(DriverManager.java:525) [java] at java.sql.DriverManager.getConnection(DriverManager.java:193) [java] at org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:717) [java] at org.dspace.storage.rdbms.DatabaseManager.loadSql(DatabaseManager.java:1062) [java] at org.dspace.storage.rdbms.InitializeDatabase.main(InitializeDatabase.java:71) Anyone have an idea? Stéphane Collin - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Persistent identifiers in DSpace -- thoughts please
On Wed, May 30, 2007 at 02:01:50AM -0400, Larry Stone wrote: How about the word resource to introduce the URI, since it is, after all, a reference to a resource -- the R in URI. It'd be: prefix/resource/encoded-URI e.g. http://dspace.me.ac.uk/resource/hdl/1234/56 This follows the proposal to encode the URI by tearing off the scheme and putting it in a separate pathname element to avoid issues over quoting the :. Note that I propose using the actual scheme label in the URL rather than a user-friendly label, e.g. hdl rather than handle. This sounds like some reasonable middle-ground. The only issue I can see here is that this mechanism only allows us to refer to objects that have persistent identifiers. Of course, we could still use an internal form of identifier for objects without actual persistent identifiers, but then if we have an internal format, should we not use that everywhere? Aside from consistency, Mark made the observation that including the persistent identifier in the URL is, to a certain extent, bogus. Perhaps we could just provide the ability to resolve URLs of the above form, but for making links, etc, we use an internal identifier format. That's a good point -- DSpace is taking on the function of resolving persistent identifiers like Handles and DOIs when there is no need, since Handles, at least, already have a Web proxy server. I wasn't counting on the add our own flavor of PIDs to DSpace getting resolved favorably.. It _does_ have to allow data model objects to be referenced (through Web interfaces) by an URL that includes a _persistent_ identifier (as opposed to, say, a database-ID). That's the URL that will get used in links and citations despite our best efforts to promote Handles, so it needs to be reasonably permanent. Given a DSpace-specific persistent identifier (e.g. the UUID scheme), I see two options: 1. Give every content-model object a DSpace-type PID, no matter what. External references are URLs including the DSpace PID. Other PID schemes (e.g. Handle) resolve to those URLs. Allow plugins to register other PIDs when an object is created. 2. Make the DSpace PID into a PersistentIdentifier plugin so it is a peer with the Handle or DOI plugins. The administrator chooses to support one or more, and the canonical external reference to an object becomes whichever kind of PID is configured to be canonical. Choice (1) is simpler and seems more sensible, but (2) could be completely backward-compatible. Note that some ingested objects will already have PIDs, e.g. if they are AIPs being re-ingested to reconstruct an archive after catastropic failure, or DIPs (AIPs) mirrored from another repository. If _all_ DSpaces have the same PID scheme as in (1), there's no problem ingesting and accessing another archive's objects. Under (2), you could end up generating new PIDs for old objects because your archive doesn't understand the kind of PID they already have. I think the UUID scheme (or something like it) makes a whole lot of sense, but it is a rather significant change. Re special characters and quoting: I agree with James' original point that the HTTP URL spec has quoting rules for just this reason, but from a practical point of view, the client and server implementations have a lot of bugs in this area. That's what I discovered implementing WebDAV for the LNI: it wasn't worth trying to encode a slash (/) in a URL, e.g. within a Handle, because it would just get stomped on differently by the different clients. Better to let it get used literally as a path element separator and make the servlet clever enough to figure it out. Also, construct the servlet's URL so the whole path after a certain point is part of the object URI, e.g. the Handle. Again, this sounds fine. The only reason this doesn't work with the current implementation with Handles is for referencing bitstreams -- we are forced to make assumptions about the structure of the persistent identifiers because we use the (arbitrary and unpredictable) filename as part of the URL. This must be avoided, whichever scheme we eventually use. Do you mean the way Bitstreams are referenced in a /bitstream/ servlet URL? I thought the path actually doesn't matter there -- it can be anything, the servlet only looks at the sequence ID, because the URL follows the pattern: prefix/bitstream/handle/SequenceID/path e.g. http://dspace.mit.edu/bitstream/1721.1/35700/2/60504128-MIT.pdf ...hmm, it didn't _used_ to care what the path was at all, it would retrieve the bitstream referenced by the Sequence ID. Now, at least on the 1.4.1 system I checked, both SID and path have to match. But it doesn't have to be implemetned that way. Since Sequence IDs are the ONLY Bitstream metadata which must be unique within an Item, the servlet might as well just ignore the path. (Of course, this ignores the necessity of the /html/ servlet which
[Dspace-tech] Highlight Search word in display record
As one of the requirement of the project is to make search word highlight in the display record or also possibly in a full text record. Whether some one has attempted it or DSpace has any plan to make search word highlight in a full text record. thanks and regards Surinder Kumar NIC, New Delhi -- Surinder Kumar Gaba Technical Director Bibliographic Informatics Division National Informatics Centre A-Block, CGO Complex, Lodhi Road New Delhi-110 003 Tel : 011-24362359 (o) : 011-27865224 (r) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
