[Dspace-tech] Language flags not used from item template
I have discovered something that I believe is a bug, or then there's something I simply don't get: language flags assigned to metadata fields in an item template seem to be ignored completely. How to reproduce (tested this with dspace 1.4.2): 1) Create an item template for a collection 2) In the template, assign a default value to Title for example, and set the language for this field to something else than your default language 3) Start submitting to the new collection: the default Title from the template shows up, all is well so far.. 4) Review the metadata of the submitted entry. Your default Title is still there, but the language flag is now set to whatever you have defined in dspace.cfg/default.language! If default.language is not set, the Title field will not have any language definition at all. So to me it appears that the default.language parameter overrides the item template languages, even when default.language is undefined. Any thoughts on this? Bug or feature? Any workaround? best regards Mathias Hjelt HANKEN - 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-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent
Hello Scott, Thanks for your note. On Tue, 2007-06-12 at 12:06, Scott Yeadon wrote: Hi Richard, It's up to you how you represent your values, you could use the DCMI Period or something simple such as 1930-1940. We tend to have the latter since that's what our users typically enter. The batch import process won't parse the values, as long as the document is valid XML the values will be accepted. Granted that using something such as: dcvalue element=date qualifier=issued1964-1970/dcvalue in one's `dublin_core.xml' file seems practical and expedient, on my system at least -- DSpace-1.4.0 -- such an approach breaks DSpace's `Browse by Title', `Browse by Date', and the offending item's `Brief View'. This is the reason I first asked the lists for details of how one should _correctly_ represent a date range in the DSpace `dublin_core.xml' file. Using `1964-1970' and so on simply does not seem to work. I have put together a series of screenshots to indicate the issues: http://indica-et-buddhica.org/sections/repositorium-preview/known-issues/dspace-item-date-ranges As you will see, I am - unhappily - coming to the conclusion that DSpace does not support item date ranges at all. It is also becoming clear that the lack of genuine validation by the item importer can easily lead to the widespread corruption of ones metadata. I hope I am wrong as these would be serious deficiencies. Best regards, Richard Mahoney Scott. Message: 3 Date: Fri, 08 Jun 2007 12:08:16 +1200 From: Richard MAHONEY [EMAIL PROTECTED] Subject: [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent To: DSpace Tech dspace-tech@lists.sourceforge.net,DSpace General [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain Dear List Members, I am in the process or preparing material for bulk import and have again encountered and issue that I was inclined to gloss over last time it arose: the format of the DSpace Dublin Core Date Elements, Qualifiers, and particularly, the Values. What exactly is the required Value format and is it configurable? Simple date Values such as the following present no difficulty: dcvalue element=date qualifier=issued1970/dcvalue The trouble for me -- and this situation would arise often for many projects -- is how to correctly represent date ranges, for e.g., date issued, 1964 to 1970. Which Value format should should be used to represent a date range in DSpace DC? Some DSpace version of the W3C-DTF/ISO 8601 scheme? http://dublincore.org/documents/2000/07/28/dcmi-period/ Best regards, Richard Mahoney -- Richard MAHONEY | internet: http://indica-et-buddhica.org/ Littledene | telephone/telefax (man.): +64 3 312 1699 Bay Road| cellular: +64 27 482 9986 OXFORD, NZ | email: [EMAIL PROTECTED] ~~~ Indica et Buddhica: Materials for Indology and Buddhology Repositorium: http://indica-et-buddhica.org/repositorium/ Philologica: http://indica-et-buddhica.org/philologica/ Subscriptions: http://subscriptions.indica-et-buddhica.org/ - 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] Oracle
Hi, Hm... I don't think this is an SQL issue, I'm suspecting some faulty data somewhere. Either your start date or end date is not of the correct format - ie. 2007-01-01 - or you have a value in your metadatavalue that isn't a valid timestamp (ie. 2007-01-01T23:01:01Z). I'm suspecting that it may be the latter. Check the start / end dates anyway, but can you execute this: SELECT text_value, decode( REGEXP_REPLACE(TO_CHAR(text_value), '([0-9])','0'), '-00-00T00:00:00Z', 1 , 0 ) AS valid FROM metadatavalue WHERE metadata_field_id = ( SELECT metadata_field_id FROM metadatafieldregistry WHERE element = 'date' AND qualifier = 'accessioned' ) ORDER BY valid, TO_CHAR(text_value); against your database. The first items to be listed will either have a badly formatted timestamp (valid will be 0), or will be an invalid value (ie. timestamp starting with ). In all other cases, the values *should* (more or less) be valid). G On Mon, 2007-06-11 at 11:32 +0200, luis jose miralls wrote: Hello ! I have a problem with oracle database. When i run the the stat-initial i get the following errors: Exception in thread main java.sql.SQLException: ORA-01841: (full) year must be between -4713 and +, and not be 0 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316) at oracle.jdbc.driver.T4CTTIoer.processError (T4CTTIoer.java:282) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185) at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows (T4CPreparedStatement.java:633) at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:984) at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java :535) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1051) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3026) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92) at org.dspace.storage.rdbms.DatabaseManager.query(DatabaseManager.java:188) at org.dspace.storage.rdbms.DatabaseManager.querySingle (DatabaseManager.java:262) at org.dspace.app.statistics.LogAnalyser.getNumItems(LogAnalyser.java:1264) at org.dspace.app.statistics.LogAnalyser.processLogs(LogAnalyser.java:535) at org.dspace.app.statistics.LogAnalyser.main (LogAnalyser.java:327) Thanks. - 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] [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent
Hi Richard I think using the date.issued field quite confusing because thats what DSpace automaticly uses when you dont check the item has been published before box. At the Institute here we used date.created and maybe I will change it for simply date. Researchers here use sometimes brackets or parentesis to indicate if a date is a guess of the researcher and all these things break the browse by date page and make the sorting alleatory. We finally decided to treat this field as text and not date (in dspace.cfg) so I remove the brackets in the field sort_date and everybody uses the -MM-DD format so periods like 1960-1970 will be sorted correctly and the browse page will not break. I hope this helps Paulo Jobim Em 12/06/2007, às 07:34, Richard MAHONEY escreveu: Hello Scott, Thanks for your note. On Tue, 2007-06-12 at 12:06, Scott Yeadon wrote: Hi Richard, It's up to you how you represent your values, you could use the DCMI Period or something simple such as 1930-1940. We tend to have the latter since that's what our users typically enter. The batch import process won't parse the values, as long as the document is valid XML the values will be accepted. Granted that using something such as: dcvalue element=date qualifier=issued1964-1970/dcvalue in one's `dublin_core.xml' file seems practical and expedient, on my system at least -- DSpace-1.4.0 -- such an approach breaks DSpace's `Browse by Title', `Browse by Date', and the offending item's `Brief View'. This is the reason I first asked the lists for details of how one should _correctly_ represent a date range in the DSpace `dublin_core.xml' file. Using `1964-1970' and so on simply does not seem to work. I have put together a series of screenshots to indicate the issues: http://indica-et-buddhica.org/sections/repositorium-preview/known- issues/dspace-item-date-ranges As you will see, I am - unhappily - coming to the conclusion that DSpace does not support item date ranges at all. It is also becoming clear that the lack of genuine validation by the item importer can easily lead to the widespread corruption of ones metadata. I hope I am wrong as these would be serious deficiencies. Best regards, Richard Mahoney Scott. Message: 3 Date: Fri, 08 Jun 2007 12:08:16 +1200 From: Richard MAHONEY [EMAIL PROTECTED] Subject: [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent To: DSpace Tech dspace-tech@lists.sourceforge.net,DSpace General [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain Dear List Members, I am in the process or preparing material for bulk import and have again encountered and issue that I was inclined to gloss over last time it arose: the format of the DSpace Dublin Core Date Elements, Qualifiers, and particularly, the Values. What exactly is the required Value format and is it configurable? Simple date Values such as the following present no difficulty: dcvalue element=date qualifier=issued1970/dcvalue The trouble for me -- and this situation would arise often for many projects -- is how to correctly represent date ranges, for e.g., date issued, 1964 to 1970. Which Value format should should be used to represent a date range in DSpace DC? Some DSpace version of the W3C-DTF/ISO 8601 scheme? http://dublincore.org/documents/2000/07/28/dcmi-period/ Best regards, Richard Mahoney -- Richard MAHONEY | internet: http://indica-et-buddhica.org/ Littledene | telephone/telefax (man.): +64 3 312 1699 Bay Road| cellular: +64 27 482 9986 OXFORD, NZ | email: [EMAIL PROTECTED] ~~~ Indica et Buddhica: Materials for Indology and Buddhology Repositorium: http://indica-et-buddhica.org/repositorium/ Philologica: http://indica-et-buddhica.org/philologica/ Subscriptions: http://subscriptions.indica-et-buddhica.org/ -- --- 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] [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent
Hello Paulo Jobim, On Wed, 2007-06-13 at 03:01, instituto A.C.Jobim wrote: Hi Richard I think using the date.issued field quite confusing because thats what DSpace automatically uses when you don't check the item has been published before box. My use of `date.issued' for previously published items is consistent with the recommendations here: http://www.dspace.org/technology/metadata.html A short summary of the suggested element / qualifier pairs follows: 1.) date -- Use qualified form if possible 2.) date accessioned -- Date DSpace takes possession of item 3.) date available -- Date or date range item became available to the public 4.) date copyright -- Date of copyright 5.) date created -- Date of creation or manufacture of intellectual content if different from date.issued 6.) date issued -- Date of publication or distribution 7.) date submitted -- Recommend for theses and dissertations Clearly, dc.date.issued is to be used for the date of `original' publication in the case of previously published material. dc.date.created, on the other hand, is only to be used in addition, and not as a substitute for, dc.date.issued. At the Institute here we used date.created and maybe I will change it for simply date. As above, probably its undoubtably best to use a qualified form if you can. Researchers here use sometimes brackets or parentesis to indicate if a date is a guess of the researcher and all these things break the browse by date page and make the sorting alleatory. We finally decided to treat this field as text and not date (in dspace.cfg) so I remove the brackets in the field sort_date and everybody uses the -MM-DD format so periods like 1960-1970 will be sorted correctly and the browse page will not break. The primary issue for me is how to represent date ranges in the dublin_core.xml file so that DSpace can adequately sort and display the range in `Browse by title' and `Browse by date', and display the range in `Brief item view'. If I properly understand the relatively few responses to my query, the short answer is that one cannot. The stock DSpace distribution does not enable one to specify a date range in an item's date metadata fields, for e.g., something along the lines of the DCMI Period Encoding Scheme: http://dublincore.org/documents/dcmi-period/ This is a serious deficiency in any system, let alone in one that has pretensions to provide a basis for a digital archive. I would welcome comments from DSpace core developers on their proposed solution to DSpace's lack of support for encoding periods. Best regards, Richard Mahoney I hope this helps Paulo Jobim Em 12/06/2007, às 07:34, Richard MAHONEY escreveu: Hello Scott, Thanks for your note. On Tue, 2007-06-12 at 12:06, Scott Yeadon wrote: Hi Richard, It's up to you how you represent your values, you could use the DCMI Period or something simple such as 1930-1940. We tend to have the latter since that's what our users typically enter. The batch import process won't parse the values, as long as the document is valid XML the values will be accepted. Granted that using something such as: dcvalue element=date qualifier=issued1964-1970/dcvalue in one's `dublin_core.xml' file seems practical and expedient, on my system at least -- DSpace-1.4.0 -- such an approach breaks DSpace's `Browse by Title', `Browse by Date', and the offending item's `Brief View'. This is the reason I first asked the lists for details of how one should _correctly_ represent a date range in the DSpace `dublin_core.xml' file. Using `1964-1970' and so on simply does not seem to work. I have put together a series of screenshots to indicate the issues: http://indica-et-buddhica.org/sections/repositorium-preview/known- issues/dspace-item-date-ranges As you will see, I am - unhappily - coming to the conclusion that DSpace does not support item date ranges at all. It is also becoming clear that the lack of genuine validation by the item importer can easily lead to the widespread corruption of ones metadata. I hope I am wrong as these would be serious deficiencies. Best regards, Richard Mahoney Scott. Message: 3 Date: Fri, 08 Jun 2007 12:08:16 +1200 From: Richard MAHONEY [EMAIL PROTECTED] Subject: [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent To: DSpace Tech dspace-tech@lists.sourceforge.net, DSpace General [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain Dear List Members, I am in the process or preparing material for bulk import and have again encountered and issue that I was inclined to gloss over last time it arose: the format of the DSpace Dublin Core Date Elements, Qualifiers, and particularly, the Values. What exactly is the required Value format and is it configurable? Simple date Values such as the following
Re: [Dspace-tech] [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent
Hi Richard, Hello Scott, Thanks for your note. On Tue, 2007-06-12 at 12:06, Scott Yeadon wrote: Hi Richard, It's up to you how you represent your values, you could use the DCMI Period or something simple such as 1930-1940. We tend to have the latter since that's what our users typically enter. The batch import process won't parse the values, as long as the document is valid XML the values will be accepted. Granted that using something such as: dcvalue element=date qualifier=issued1964-1970/dcvalue in one's `dublin_core.xml' file seems practical and expedient, on my system at least -- DSpace-1.4.0 -- such an approach breaks DSpace's `Browse by Title', `Browse by Date', and the offending item's `Brief View'. This is the reason I first asked the lists for details of how one should _correctly_ represent a date range in the DSpace `dublin_core.xml' file. Using `1964-1970' and so on simply does not seem to work. It's likely that this is because the default metadata display is not able to render date ranges properly. In your DSpace config file put the following entry: webui.itemdisplay.default = dc.title, dc.title.alternative, dc.contributor.*, dc.subject, dc.date.issued, dc.publisher, dc.identifier.citation, dc.relation.ispartofseries, dc.description.abstract, dc.description, dc.identifier.govdoc, dc.identifier.uri(link), dc.identifier.isbn, dc.identifier.issn, dc.identifier.ismn, dc.identifier The date.issued field is by default formatted to a date (see ItemTag.java for the hardcoded list) using the dc.date.issued(date) field display text. Removing the (date) part of this will stop any special rendering taking place. Also, setting: webui.itemlist.columns = dc.date.issued, dc.title, dc.contributor.* in the dspace.cfg file may also resolve your ranges not showing up in the browse page (the default specifies dc.date.issued(date)), so as above removing the rendering rules should fix this) There should also be a section in the docs covering the above config items you could have a look at, since you may also want to customise your simple view and browse columns. I have put together a series of screenshots to indicate the issues: http://indica-et-buddhica.org/sections/repositorium-preview/known-issues/dspace-item-date-ranges As you will see, I am - unhappily - coming to the conclusion that DSpace does not support item date ranges at all. It is also becoming clear that the lack of genuine validation by the item importer can easily lead to the widespread corruption of ones metadata. I hope I am wrong as these would be serious deficiencies. I imagine the reason validation is not included is that DSpace in general doesn't set down value format rules, since every institution is likely to have differing requirements. Having said that, there is no easy plugin to set your own rules, you would have to modify the import process to support this if you needed it, or pre-process your material prior to loading to apply any rules you need enforced. Hope that helps. Scott. Best regards, Richard Mahoney Scott. Message: 3 Date: Fri, 08 Jun 2007 12:08:16 +1200 From: Richard MAHONEY [EMAIL PROTECTED] Subject: [Dspace-general] DSpace `Dublin Core' | Date Issued | Date Range | How to represent To: DSpace Tech dspace-tech@lists.sourceforge.net,DSpace General [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain Dear List Members, I am in the process or preparing material for bulk import and have again encountered and issue that I was inclined to gloss over last time it arose: the format of the DSpace Dublin Core Date Elements, Qualifiers, and particularly, the Values. What exactly is the required Value format and is it configurable? Simple date Values such as the following present no difficulty: dcvalue element=date qualifier=issued1970/dcvalue The trouble for me -- and this situation would arise often for many projects -- is how to correctly represent date ranges, for e.g., date issued, 1964 to 1970. Which Value format should should be used to represent a date range in DSpace DC? Some DSpace version of the W3C-DTF/ISO 8601 scheme? http://dublincore.org/documents/2000/07/28/dcmi-period/ Best regards, Richard Mahoney - 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] File Storage
Hi, I want to store the assets(bit stream) on another server but not the DSpace application server . I know SRB server can do this,but I don't plan to use SRB server because it is not opensource. Is there any other solution? Thanks in Advance. Jimmy - 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] Setting Primary Bitstream
While uploading multiple files (html files and other links files) using batch import facilty, DSplace displays all the files. While going through archive it is found in the mail That's still true for the batch importer AFAIK, but there is now another way to ingest an Item that will let you set the primary bitstream. If you make a METS package, which means creating a METS manifest and putting it into a Zip file with the content files, then you can use the package ingester. You can declare the primary bitstream in the METS manifest, see: http://wiki.dspace.org/index.php/DSpaceMETSSIPProfile The package ingester can be run from the command line like the batch importer, although it only handles one package at a time. For details about the package ingester, see the system doc: http://dspace.svn.sourceforge.net/viewvc/*checkout*/dspace/trunk/dspace/docs/application.html#packager The easiest way to get an example is to take an item alraedy in the archive which is similar to what you want, and export it as a METS package using the command-line packager, then look at its METS manifest. -- Larry Message: 3 Date: Mon, 11 Jul 2005 18:15:59 EDT From: Larry Stone [EMAIL PROTECTED] Reply-To: Larry Stone [EMAIL PROTECTED] To: Jim Downing [EMAIL PROTECTED] Cc: PRAT [EMAIL PROTECTED], dspace-tech dspace-tech@lists.sourceforge.net Subject: RE: [Dspace-tech] (no subject) You have to set the primary bitstream for the item, manually, to the top-level web page -- e.g. usually index.html. The ItemImporter doesn't have any way to set a primary bitstream, although this seems like a very good thing to add. The only way I know to do this is in the administrative GUI for the Item. Whether DSpace has any plan to solve this problem in coming version?. 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 - 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
