Re: [Dspace-devel] DSpace 4 massive public/private change
Hi Carlos, DSpace version 4 uses Solr search by default. If you did not change this setting, you should run [dspace]/bin dspace index-discovery -f Regards, Keiji Suzuki 2014-04-11 0:45 GMT+09:00 Carlos Alonso Vega los...@unavarra.es: Hi, I was trying to make a bulk change from private to public of multiple items but I did not succeed. It seems that field discoverable on item table is the switch for making an item private or not. Changing the field with sql queries and reindexing (index-db-browse -f -r -v and index-lucene-init) does not makes any effect (no previous public/private items change their behaviour in browse lists) I am a bit stuck on this as I did not find any other relevant field on db that could be related. Any help or ideas will be appreciated Carlos -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- 鈴木敬二＠江別市 -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1963) Making a item private, never becomes public again
Title: Message Title Denis Fdz commented on an issue Re: Making a item private, never becomes public again Close, this issue. There is no problem with this. I have checked it again, and I think that the delay changing item's state, while the search indexes are updated, was the problem that makes me thought it doesn't work. Sorry for the inconvenience. Add Comment DSpace / DS-1963 Making a item private, never becomes public again Making a item private through the Edit Item interface, never will become public again. You can try with any item at demo.dspace.org. Also, I think that could be recommendable to add one more step for making item public, like when making item private. Something such as CONFIRM_PUBLICIZE, which redirects to a jsp asking for a confirmation for making... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud.
Re: [Dspace-devel] DSpace 4 massive public/private change
Hi Keiji, Thanks a lot for for help. You were right, that was what I needed. I messed myself a bit with indexing options. Carlos El 11/04/2014 9:05, SUZUKI Keiji escribió: Hi Carlos, DSpace version 4 uses Solr search by default. If you did not change this setting, you should run [dspace]/bin dspace index-discovery -f Regards, Keiji Suzuki 2014-04-11 0:45 GMT+09:00 Carlos Alonso Vega los...@unavarra.es: Hi, I was trying to make a bulk change from private to public of multiple items but I did not succeed. It seems that field discoverable on item table is the switch for making an item private or not. Changing the field with sql queries and reindexing (index-db-browse -f -r -v and index-lucene-init) does not makes any effect (no previous public/private items change their behaviour in browse lists) I am a bit stuck on this as I did not find any other relevant field on db that could be related. Any help or ideas will be appreciated Carlos -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1963) Making a item private, never becomes public again
Title: Message Title Tim Donohue closed an issue as Cannot Reproduce Closing this ticket as it was just a small delay in updating search indexes. DSpace / DS-1963 Making a item private, never becomes public again Change By: Tim Donohue Resolution: CannotReproduce Status: Received Closed Add Comment This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1969) How to create dspace database objects in other schema (not public schema) in Postgres
Title: Message Title Divino Ignacio Ribeiro Jr created an issue DSpace / DS-1969 How to create dspace database objects in other schema (not public schema) in Postgres Issue Type: Documentation Affects Versions: 3.2 Assignee: Unassigned Created: 11/Apr/14 8:51 PM Environment: CentOS; Postgres lastest version Labels: database Priority: Major Reporter: Divino Ignacio Ribeiro Jr Original Estimate: 4 days Remaining Estimate: 4 days How to create dspace database
Re: [Dspace-devel] jspui and xmlui in the long run
Sorry to bump an old thread. XMLUI and JSPUI are quite solid and both provide a complete package as a repository interface, they don't maintain parity and don't have to, but there are interested parties that make the needed investments in each, that I don't see either dissolving in the short term. DSpace today presents a lot of work to build yet-another-user-interface. I think that with the current REST-API this has changed for the frontend end-user browsing experience. There are a few experiments of client apps to the API, and this is where the future of DSpace becomes a bit more interesting. If 99% percent of your traffic is the anonymous end-user, then why not build an application well suited for delivering an experience that delights visitors, and helps expose your content. (API provides read access to public communities, collections, items, and bitstreams) Ruby on Rails client app: http://dspace-rails.herokuapp.com/item/59996 Java Play! client app: http://dspace-rest-client-play.herokuapp.com/item/59996 For the remaining 1% of users, your administrators, editors, submitters, I haven't yet begun work on functionality in the REST-API to support any of their needs, so my first thought would be to leverage one of the existing user interfaces, and just hand the user back to (jsp|xml)ui for the advanced features. This route certainly seems a bit too cutting edge for a casual repository, but once more groundwork has been laid in the API, building a complete UI might not be such a chore. Long response to your question, but I would say there are contributors to both xmlui and jspui, that I see both ui's sticking around for the next few releases. Even once REST-API of the future emerges, jspui and xmlui could be refactored to use/send all data through the rest API. On Oct 9, 2013 5:36 PM, helix84 heli...@centrum.sk wrote: On Wed, Oct 9, 2013 at 11:23 PM, Claudia Juergen claudia.juer...@ub.tu-dortmund.de wrote: Meanwhile the community has grown and both UI's are used and developed not in sync but on a more or less equal level. So, apart from completely new developments, can one assume, that for the next couple of releases both UI's will be supported? Hi Claudia, it definitely seems so. There are both users and commiters who use both JSPUI and XMLUI and at any point in time, one or the other is in ahead development in some respects, but overall, both progress steadily. I'm confident this will continue to be so for the next few years and when someone starting with DSpace asks which one is better, I recommend them to 1) choose based on features currently available, if there are some UI-specific ones they need 2) if they're going to do more than basic customization, go with the technology they're most familiar with (JSP vs. XSLT). In the future, with Solr and REST API, I foresee that this landscape will become even more diverse with other UIs (maybe task-specific ones, not necessarily full-featured) popping up, written in other popular languages/platforms. Regards, ~~helix84 -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
