[Dspace-tech] Batch Import and Namespaces
Hi all, I'd like to import several documents and their meta data into DSpace. I found the preparation tool 'csv_import' by Mika Stenberg and the import description at http://www.dspace.org/index.php?option=com_contenttask=viewid=144#importingitems . According to the description of this tools all used meta data elements (= field names) used in the CSV must be declared first in a meta data scheme of the collection to which the data should be imported. For our application I defined several new meta data elements and a second namespace too (besides the default 'dc' namespace (Dublin Core core elements) I introduced the 'dct' (Dublin Core Types) too). My problem is now, that the import via 'dsrun org.dspace.app.itemimport.ItemImport' is not able to handle more then 1 schema (besides the problem that I don't see any possibility to change the default 'dc' to an alternative scheme). Does someone came across the same situation? Does someone knows a way to do it? Best regards Robert -- === Robert Roggenbuck Universitaetsbibliothek Osnabrueck Germany === - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Email SSL trouble
On Thu, Nov 08, 2007 at 07:41:02AM +0100, Christian Voelker wrote: Am 06.11.2007 um 20:17 schrieb Douglas Ramiro: Hello Everybody. I'm in trouble with emails. I configured my dspace with a smtp server that dont use SSL. It works fine. But at my institute, the email server use SSL and dspace dont send email. What can I do? I cant see how this makes any trouble. As I understand it, smtp servers dont communicate over TLS between each other but provide this method only for sending from the MUA to protect your credentials in case you have to authenticate to the server. Two MTAs certainly *can* use either SSMTP or STARTTLS to communicate via an encrypted channel. Whether there is any pair of MTAs configured so that they *do* is another question. Any SMTP that I set up, MTA or MUA, will offer or attempt STARTTLS, but I know it isn't universal practice. If the MTA that Mr. Ramiro must use is configured to demand SSL then he must supply SSL. To do this, one must either configure JavaMail to offer SSL, or do what I do: install an MTA under one's own control on Tomcat's host and set it up to offer SSL when forwarding to the institutional email hub. There doesn't seem to be a way to tell JavaMail to request SSL using dspace.cfg parameters. It would be necessary to set mail.smtp.starttls.enable = true in the Properties passed to Session.getInstance() or Session.getDefaultInstance(), but we'd need support from DSpace to do that. So it appears that this method is not usable with DSpace 1.4.1, which is the latest I have running. It would be good for someone to file a feature-request for this, or even a patch. Then one would need to set up a certificate store for the account used to run the servlet container, so that JavaMail can validate the MTA's certificate. On the other hand, setting up an MTA without creating problems such as an open SMTP relay requires great care and much reading. If you don't already know how to set up an MTA then I would suggest getting help with the specific MTA you choose. Further problems you may encounter: o It is possible that the institutional MTA requires a client certificate to prove that it is talking with a known partner. I've never seen this done, but it could be done. If so, you will need to work with that MTA's administrators to provide what it is expecting. o One reason to require SSL is that the MTA also requires AUTH PLAIN or AUTH LOGIN authentication. These methods send the credentials in plaintext, meaning that valuable passwords are exposed on the network. Encryption by SSL protects the passwords. So you may find that you have a functioning SSL connection but now you need to supply credentials. Again you may need to negotiate this with the MTA's admin.s. Some MTAs will refuse plaintext AUTH mechanisms over an unencrypted connection but will accept other AUTH mechanisms without encryption. JavaMail can do AUTH DIGEST-MD5, so if that is acceptable to the institutional MTA without encryption, and you don't have any other requirement for encryption, then this may be sufficient. Finally, you might be able to negotiate the use of unencrypted SMTP from your specific host as an exception to the general rule. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is intuitive he means the exact opposite. pgpbLzcdPnCD5.pgp Description: PGP signature - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Duplicate items in browse items by author
I've come up with a temporary solution that works (at least it does today) on the items that we (currently) have. In the Dspace source, I modified our org.dspace.browse.Browse so that the getTargetColumns method contains these lines: else if (browseType == ITEMS_BY_AUTHOR_BROWSE) return distinct item_id, sort_author; This gave me the correct number of results, but it seems to break the sort by titles feature of this browse. So in the Manakin source, I modified our BrowseAuthorItems class in the ArtifactBrowser aspect so that the addBody method sorts the results according to the dc.title element: Item[] items = browseInfo.getItemResults(); Arrays.sort(items, new ItemComparator(title, null, Item.ANY, true)); We're also checking with our library liaison if it would be acceptable to remove the dc.contributor element from the metadata when the value is identical to the value in dc.contributor.author. There are concerns about both of these approaches, so I'm still open to other ideas about how to handle the situation. I've also received a patch from Christophe Dupriez that fixes issues with duplicate items in the jsp interface. I can forward it along to anyone who would like to try this route. Keith Gilbertson Systems Developer Ohio Library and Information Network _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith Gilbertson Sent: Thursday, November 08, 2007 10:46 AM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Duplicate items in browse items by author Hello, I'm working on troubleshooting an issue with an installation of DSpace 1.4.2 and Manakin 1.1. When browsing items by certain authors, the items appear twice in the artifact list. An example can be seen here: http://drc.libraries.wright.edu/browse-author-items?author=The+Dayton-Wright +Airplane+Company The items by this author were added to the collection via the DSpace ItemImport tool, but this is also occurring for items that were submitted manually by users through the Manakin web interface. When I examine the full item records for these items that are being listed twice in the items by author browse, I see information similar to the following: contributor: The Dayton-Wright Airplane Company en_US contributor.author: The Dayton-Wright Airplane Company en_US contributor.institution: Wright State University There are three contributor fields and two of them have the same value. When I look in the itemsbyauthor table in the database, I see the following for one of these items: items_by_author_id | item_id |author| sort_author +-+--+-- 4787 | 115 | The Dayton-Wright Airplane Company | the dayton-wright airplane company 4788 | 115 | The Dayton-Wright Airplane Company | the dayton-wright airplane company 4789 | 115 | Wright State University | wright state university Each item_id appears three times, including two times with the same author - once for the contributor field and once for the contributor.author field. Has anyone dealt with items displaying multiple times in browse by author views, and how did you handle it? Are multiple occurrences of the same item with the same author in the itemsbyauthor table allowed by design? What would be the best way for us to fix this on our installation? I've collected some ideas but I'm unsure of all of the consequences. - Change the metadata for our items so that the unqualified contributor element is not used. Contributor.author may be sufficient. - Change the XSLT that creates the browse table to check if the current item is a duplicate of the previous sibling before displaying it. The problem also exists with the JSP interface, but we use only the Manakin interface. - Change the underlying database query for browsing items by author so that only tuples with distinct item_id values are returned - Change the item submission tools so that the author/item_id combination is not duplicated between rows in the itemsbyauthor table guidance on a solution. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
