Re: [Dspace-tech] Differences between the data model and the trunk
Mark, I have understanding you opinion but I'm not really sure that the owning collection is a relationship in the actual model or that we need a similar relationship in future development. At the moment we need owning collection only for keep simple some presentation (display style, bread crumbs) authorization choice, looking forward I think that all collections where the item is mapped really own the item, the item mapper feature should check not only for ADD permission on the target collection but also for ADMIN permission on the item self. Presentation issue should be resolved in their domain: bread crumbs should show the path used by the user for get the item, display should be based only on the item metadata so. I propose to rename OwningCollection in SubmittedCollection to keep live this info (as for submitter) also after that the inProgressSubmission became an Archived Item. With this approach SubmittedCollection has to be considerate an item attribute and not a relationship... (the SubmittedCollection could be also not an own of the item after some time) Andrea Mark Diggory ha scritto: On Nov 20, 2007, at 3:55 AM, Andrea Bollini wrote: Larry Stone ha scritto: Collection * - * Item It's worth noting that while an Item may be a member of multiple Collections, it still refers to only one of them as its owner; it is returned by getOwningCollection(). true but IMHO this is not really needed... Well, what I've suggested in my previous email is not wether it is needed or not, but where it should correctly reside in relational terms, owner is a relationship, not an attribute of Item and Collection, thus the more appropriate location would be in the container or relationship tables. I.E. rather than: --- -- Item table --- CREATE TABLE Item ( item_id INTEGER PRIMARY KEY, submitter_idINTEGER REFERENCES EPerson(eperson_id), in_archive BOOL, withdrawn BOOL, last_modified TIMESTAMP WITH TIME ZONE, owning_collection INTEGER ); --- -- Collection2Item table --- CREATE TABLE Collection2Item ( idINTEGER PRIMARY KEY, collection_id INTEGER REFERENCES Collection(collection_id), item_id INTEGER REFERENCES Item(item_id), ); instead have --- -- Item table --- CREATE TABLE Item ( item_id INTEGER PRIMARY KEY, submitter_idINTEGER REFERENCES EPerson(eperson_id), in_archive BOOL, withdrawn BOOL, last_modified TIMESTAMP WITH TIME ZONE ); --- -- Collection2Item table --- CREATE TABLE Collection2Item ( idINTEGER PRIMARY KEY, collection_id INTEGER REFERENCES Collection(collection_id), item_id INTEGER REFERENCES Item(item_id), owning_collection BOOL ); Ownership is a relationship and not a attribute and the dependency is one way. This also is an example that enforces third normal form because you cannot have a owning collection for which the item is not a member. (Although you can have multiple owners). When an Item is accessed directly, by itself without the navigational context of one of the Collections it belongs to, it consults the owning Collection for display style this is only one possibility and it is not the most useful (see MedataStyleSelection in 1.5) Very true and we will see that Manakin will mix this up even more. and policies (e.g. access control by Collection admins). the auth system need a lot of work, in my path community admin that introduce some hierarchy control I have used the owning collection as the only real parent i.e. if I want modify the item but I have not direct permission I check for ADMIN right on owning collection... this is not optimal, if we have an item mapped in an other collection I think that only directly authorized people or ADMIN of both collection should manage it For Daniele works I recommend to keep ownCollection in place but I think that we need to remove it in future version. PS:the concept of owning collection is used also in workflow and submission system but there is a main difference: the data are stored in inProgressSubmission object not in the item object. Also in this case I hope that we can introduce a more modular way to select workflow process and submission process then simply use the owning collection. Andrea Andrea, that is another example of what I speak of above. At least in this case, we see
Re: [Dspace-tech] streaming video?
Hi Andrea, Thanks - the patch looks useful. Naveed --On 22 November 2007 10:33 +0100 Andrea Bollini [EMAIL PROTECTED] wrote: Hi Naveed, I have not really expertise on this topic but I have posted of patch that should make more simple add similar features in dspace in a more modular way. Please take a look at http://sourceforge.net/tracker/index.php?func=detailaid=1817742group_id =19984atid=319984 Andrea NS Hashmi, Information Systems and Computing ha scritto: Hi, Is there any one using DSpace to store and stream video files? Thanks, Naveed Naveed Hashmi Information Systems and Computing University of Bristol - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Dott. Andrea Bollini Responsabile tecnico sviluppo e formazione applicativi JAVA Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it cel. +39 348-8277525 Naveed Hashmi Information Systems and Computing University of Bristol [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Error trying to delete community
Hi I am trying to delete an empty community which we created earlier on our system. I get the following internal server error: An internal server error occurred on http://digispace.uj.ac.za:8080/dspace: Date: 07/11/22 02:29 Session ID: 8DE089088EF43383E9075BFBC7136A7A -- URL Was: http://digispace.uj.ac.za:8080/dspace/tools/edit-communities -- Method: POST -- Parameters were: -- action: 2 -- submit: Delete this Community... -- community_id: 5 Exception: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.ja va:572) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja va:305) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc her.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio nDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp atcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat cher.java:301) at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:91) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditC ommunitiesServlet.java:190) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet. java:147) at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105 ) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnly Filter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1 48) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:86 9) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.proc essConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint .java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow erWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:684) at java.lang.Thread.run(Thread.java:595) Seems to be a Java error. I reindexed and vacuumed the database. No success. Any ideas? Barrie Swanepoel IT Coordinator Library and Information Centre University of Johannesburg PO Box 524 Aucklandpark 2006 Johannesburg Republic of South Africa Tel +27 11 5592347 Fax +27 11 726 7723 Email [EMAIL PROTECTED] image001.jpg- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Work Study Opportunity - The Banff Centre (Digital Repository)
Of possible interest -Original Message- Digital Repository Work Study http://www.banffcentre.ca/programs/program.aspx?id=667 Program dates: January 21, 2008 - March 17, 2008 Application deadline: December 10, 2007 Preserving digital assets and content is one of the most significant challenges facing institutions and organizations throughout the world. Enormous amounts of digital information have already been lost forever. Digital evolution has been too rapid and costly for governments and institutions to develop timely and informed preservation strategies. The threat to the economic, social, intellectual and cultural potential of the heritage - the building blocks of the future - has not been fully grasped...unless the prevailing threats are addressed, the loss of the digital heritage will be rapid and inevitable. - UNESCO Charter on the Preservation of the Digital Heritage The Digital Repository Work Study program is an exciting opportunity to learn and develop experience in this cutting-edge and challenging field. Participants will be given direct hands-on experience in implementing technology solutions to support the long-term preservation of digital assets. They will be provided with an opportunity to implement and test a range of open-source and commercial applications, including DSpace (MIT), Fedora (Cornell University), Greenstone (New Zealand), DAITSS (Florida State), and ContentDM (OCLC). Learning opportunities may also include research into emerging standards, challenges, and technical innovations related to digital preservation. This work study opportunity is intended for individuals with working knowledge and experience in SE Linux/Unix, Tomcat, Apache, PostgresSQL, Perl, and Java. Participants will work as part of a team that includes system administrators, programmers, archivists and librarians. Participants accepted to the work study program will receive a scholarship to cover the program fee and are awarded a weekly stipend to offset the costs associated with room and board during the program. Work study programs are intended to provide participants with a combination of learning opportunities and supervised, practical work related to the participant's learning objectives. Participation in a work study term is considered to be full-time study, rather that employment. All participants sign a learning contract that assists in the evaluation of their work study experience. Scholarship stipend payments are not specifically linked to work performed or performance but are intended to enable participants to pursue the overall learning objectives. All applications must include: * A completed application form; * A non-refundable application processing fee of $59 Cdn, payable to The Banff Centre; * A current résume; * Two letters of reference, or the names, addresses, and telephone numbers of two references who are willing to support the candidate's application and professional development objectives. Application details: http://www.banffcentre.ca/programs/program.aspx?id=667p=apply -- MacKenzie Smith Associate Director for Technology MIT Libraries - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Development goals
Dorothea, I think there's an additional issue that may prove even more difficult to address: the problem of a technical infrastructure widely adopted by non-technical people. We should establish that this is actually the norm (as you point out later) and in every industry, not just libraries or archives. Business managers theoretically know what they need, but do not (should not) be expected to write the software to accomplish those goals. I haven't taken a look at the wiki to be sure, but my gestalt sense is that a substantial majority of DSpace instances live in academic libraries and academic-library consortia. As the general run of academic librarians goes, *I am highly technical*. (Tim Donohue is an outright anomaly.) I think you're right that the majority of DSpace adopters right now are in the library or related domains. At least the visible ones. But those institutions are taking various approaches to defining and managing their repository services. Some have one-person-to- do-everything, and some have much more fine-grained support. As one example, at MIT we have a dedicated product manager (not hands-on technical, but quite capable of writing requirements and talking to developers), a dedicated developer, and a sysadmin to look after the production system day-to-day. I wish I had more staff to help out, but this is what we could support for the moment. The one-person-who-does-it-all model is definitely not going to scale for the sorts of DSpace applications that we're seeing. And if you look at the staffing models for other production systems like ILSes or course management systems no one would expect one person to deal with every aspect of them (including writing the software). These are complex problems that we're just beginning to understand, so expect to see plenty of dead ends and throw-away code before it's over. In other words, *more* investment, not less, at this stage of the game. As I said, though, I'm atypical *on the technical high end* of librarianship. I don't think DSpace has ever come to terms with what that means. It's not end-user cluelessness that's the problem, as it is with many open-source packages. It's cluelessness *in the managers of the software*, which is a different and rather nastier problem. I will argue strenuously that service managers (or product managers, or program managers, or whatever you prefer to call that role) should *not* be trying to hack the system. They should be, and are, asking for changes that they think will improve the service they run. But who to ask? There are two paths: ask local developers (MIT's case) or ask the DSpace developer community at large. Obviously the former has a better chance of actually getting done, but the latter happens sometimes. For example, your request for an easier, less technical way to configure the system that doesn't require programming skills is very reasonable, but it would take a developer a lot of time to implement that, and it would be to the benefit of the whole community rather than a single institutions (especially the ones that have developers who might do this work, but who don't particularly need it themselves). So how to get that done? You could hire a developer of your own to do it. Or talk your institution (or CIC) into pooling its resources to hire a developer at the Foundation to do the work. etc. - Since discussion of DSpace development is (understandably!) heavily tilted toward developers and people with developer-level skills, the developer community has very little access to and therefore comprehension of rubber-meets-road requirements and procedures in real-world library contexts. Also a generalization. Many DSpace developers are confronted daily with local service managers that want stuff. The problem as I see it is that those product roadmaps aren't being widely shared by their service managers (at least not on the DSpace lists) so we don't know where they converge or differ. That's what I'd like to see improved, but I wonder how much agreement there really is between institutions about the right way for repository services to evolve... what you perceive as indifference from developers may actually be indifference from the service managers that decide what those developers should work on... so you may be arguing with the wrong people. - It has historically been extremely difficult for an individual at my level of technical savvy or below to be heard by DSpace developers. So (not to belabor the point) but could you ask Ken and Nolan to give you a dedicated developer for a year? If repository services are a priority for your institution, can you make the case that you need more resources to do what you believe it should? On the other hand, open-source developers are notorious for disdain of non-technical input and the people who provide it, and DSpace has unfortunately not departed from that pattern. I know most of
Re: [Dspace-tech] Development goals
Hi Mark, I've been saying for some time that, nice as the DSpace user interface is in many respects, it is not and should not be the only way to plumb a DSpace archive. If it is (currently) difficult to get a particular search style put into DSpace, may I suggest trying a different approach. One could harvest metadata via the PMH responder, organize them any way one wishes, and search them in any desired way. I can't resist pointing out that this is exactly what DWell does -- the faceted browsing and search UI that is layered over DSpace via an OAI-PMH plugin for RDFized metadata. See http://simile.mit.edu/wiki/Dwell or Richard Rodger's presentation on same at http://www.aepic.it/conf/viewpaper.php?id=212print=1cf=11 I think this is an excellent approach to building better DSpace UIs, and just leaves us with the problem of the underlying data rigidity, which I hope we can address by relying more on RDF or other rich metadata that is stored in the assetstore alongside the content files. The current DSpace metadata tables are great for managing content, but suboptimal for discovering what's in the repository (assuming we can get better discovery metadata from outside the system, somehow). MacKenzie -- MacKenzie Smith Associate Director for Technology MIT Libraries - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Manakin messages not displaying to some users
Hi, We're having some problems regarding the i18n tags. It appears that some users acessing our repository are getting the keys and not the message. It seems that this behaviour is not linked to a specific browser/version, as in my PC it shows wrongly using an older version of Netscape only (and Firefox mode in the newest version). However, with other people it happens even with IE and Firefox (newest versions). We suppose it has to do with personal options because of the apparent randomness, but we have no idea of what options. Any ideas or suggestions? Thanks. Rafael - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Facetted / faster browsing [was Development goals]
Christophe, you might like to take a look at PKP Harvester, which uses OAI-PMH to extract metadata from institutional repositories, and can be searched (including by SRW), browsed, and harvested (via OAI-PMH). It also provides RSS feeds as a format for search results. For instance, see http://nzresearch.org.nz/ Regards Conal On Fri, 2007-11-23 at 05:29 +0100, Christophe Dupriez wrote: Hi MacKenzie, Mark and Jim! Thanks for insisting on the idea of a client based interface! DWELL: I will explore Dwell further. I tried it with http://simile.mit.edu/longwell/demo/libraries/ but it is rather slow from here. Is the inventory of values for a given facet evaluated locally, in DSpace or in an intermediary server application? I understood Dwell is based on OAI-PMH but there is no Search request in OAI-PMH. An extension has be defined for this: http://www.dlese.org/dds/services/oai2-0/odl_service_documentation.jsp but I suppose it is not part of DSpace (am I wrong?). OAI-PMH+Search(ODL) has similar capabilities than RSS and would ensure better metadata transmission. RSS: Mark+Jim advice opened my eyes on a simple fact: RSS standard(s) may be used to represent a DSpace search result set (if I add a RSS flow generation to DSpace search). The nice thing with RSS is the potential promise of subscription for searches where new records are regularly retrieved and highlighted. RSS clients are not completely aware of their potential for databases searches (and not only news feed) and could be improved to manage easily simple ad hoc searches and not only subscriptions to searches. Some of them have the three frames interface I wish for my users to browse DSpace results (like an e-mail management software). I made some experiments with RSSBandit (open-source: http://www.rssbandit.org/ ) and I think it is a possible way to go. Anybody digged in that direction? Christophe MacKenzie Smith a écrit : Hi Mark, I've been saying for some time that, nice as the DSpace user interface is in many respects, it is not and should not be the only way to plumb a DSpace archive. If it is (currently) difficult to get a particular search style put into DSpace, may I suggest trying a different approach. One could harvest metadata via the PMH responder, organize them any way one wishes, and search them in any desired way. I can't resist pointing out that this is exactly what DWell does -- the faceted browsing and search UI that is layered over DSpace via an OAI-PMH plugin for RDFized metadata. See http://simile.mit.edu/wiki/Dwell or Richard Rodger's presentation on same at http://www.aepic.it/conf/viewpaper.php?id=212print=1cf=11 I think this is an excellent approach to building better DSpace UIs, and just leaves us with the problem of the underlying data rigidity, which I hope we can address by relying more on RDF or other rich metadata that is stored in the assetstore alongside the content files. The current DSpace metadata tables are great for managing content, but suboptimal for discovering what's in the repository (assuming we can get better discovery metadata from outside the system, somehow). MacKenzie - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Conal Tuohy New Zealand Electronic Text Centre www.nzetc.org - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Error trying to delete community
Hi Sorry for resending, but I send the previous one as html so I do not think people read it. I am trying to delete an empty community which we created earlier on our system. I get the following internal server error: An internal server error occurred on http://digispace.uj.ac.za:8080/dspace: Date: 07/11/22 02:29 Session ID: 8DE089088EF43383E9075BFBC7136A7A -- URL Was: http://digispace.uj.ac.za:8080/dspace/tools/edit-communities -- Method: POST -- Parameters were: -- action: 2 -- submit: Delete this Community... -- community_id: 5 Exception: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:572) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:305) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.dspace.app.webui.util.JSPManager.showJSP(JSPManager.java:91) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:190) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:147) at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Seems to be a Java error. I reindexed and vacuumed the database. No success. Any ideas? Barrie Swanepoel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Facetted / faster browsing [was Development goals]
Hi MacKenzie, Mark and Jim! Thanks for insisting on the idea of a client based interface! DWELL: I will explore Dwell further. I tried it with http://simile.mit.edu/longwell/demo/libraries/ but it is rather slow from here. Is the inventory of values for a given facet evaluated locally, in DSpace or in an intermediary server application? I understood Dwell is based on OAI-PMH but there is no Search request in OAI-PMH. An extension has be defined for this: http://www.dlese.org/dds/services/oai2-0/odl_service_documentation.jsp but I suppose it is not part of DSpace (am I wrong?). OAI-PMH+Search(ODL) has similar capabilities than RSS and would ensure better metadata transmission. RSS: Mark+Jim advice opened my eyes on a simple fact: RSS standard(s) may be used to represent a DSpace search result set (if I add a RSS flow generation to DSpace search). The nice thing with RSS is the potential promise of subscription for searches where new records are regularly retrieved and highlighted. RSS clients are not completely aware of their potential for databases searches (and not only news feed) and could be improved to manage easily simple ad hoc searches and not only subscriptions to searches. Some of them have the three frames interface I wish for my users to browse DSpace results (like an e-mail management software). I made some experiments with RSSBandit (open-source: http://www.rssbandit.org/ ) and I think it is a possible way to go. Anybody digged in that direction? Christophe MacKenzie Smith a écrit : Hi Mark, I've been saying for some time that, nice as the DSpace user interface is in many respects, it is not and should not be the only way to plumb a DSpace archive. If it is (currently) difficult to get a particular search style put into DSpace, may I suggest trying a different approach. One could harvest metadata via the PMH responder, organize them any way one wishes, and search them in any desired way. I can't resist pointing out that this is exactly what DWell does -- the faceted browsing and search UI that is layered over DSpace via an OAI-PMH plugin for RDFized metadata. See http://simile.mit.edu/wiki/Dwell or Richard Rodger's presentation on same at http://www.aepic.it/conf/viewpaper.php?id=212print=1cf=11 I think this is an excellent approach to building better DSpace UIs, and just leaves us with the problem of the underlying data rigidity, which I hope we can address by relying more on RDF or other rich metadata that is stored in the assetstore alongside the content files. The current DSpace metadata tables are great for managing content, but suboptimal for discovering what's in the repository (assuming we can get better discovery metadata from outside the system, somehow). MacKenzie begin:vcard fn:Christophe Dupriez n:Dupriez;Christophe org:DESTIN inc. SSEB adr;quoted-printable:;;rue des Palais 44, bo=C3=AEte 1;Bruxelles;;B-1030;Belgique email;internet:[EMAIL PROTECTED] title:Informaticien tel;work:+32/2/216.66.15 tel;fax:+32/2/242.97.25 tel;cell:+32/475.77.62.11 note;quoted-printable:D=C3=A9veloppement de Syst=C3=A8mes de Traitement de l'Information x-mozilla-html:TRUE url:http://www.destin.be version:2.1 end:vcard - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
