[dspace-tech] Re: Use advanced filters in custom search form on DSpace homepage
Hi all, I'd like to reopen Jakub's question. I've just been asked to prepare custom search form in our DSpace (version 5) to allow users to search specific fields like title, author, keywords etc. I understand the concept of the filters in DSpace (search for a general term and then filter results), but it doesn't help me a lot in my specific case, because I can search for "foo" and then, when I want to search "foo" only in dc.title, I must(?) add a new filter Title contains "foo". I can see how the GET parameters in such URL looks like and I can construct such URL, but I must(?) send the query string two times (via two different GET parameters) - that complicates the creation of a simple custom form search. I can do that using javascript, however, is there any way how to do it easier? Regards, Vlastik -- -------- Vlastimil Krejčíř Library and Information Centre, Institute of Computer Science Masaryk University, Brno, Czech Republic Email: krejcir (at) ics (dot) muni (dot) cz Phone: +420 549 49 3872 OpenPGP key: https://kic-internal.ics.muni.cz/~krejvl/pgp/ Fingerprint: 7800 64B2 6E20 645B 56AF C303 34CB 1495 C641 11B9 Dne úterý 21. února 2017 17:22:54 UTC+1 Jakub Řihák napsal(a): > > Hello everybody, > > we are using DSpace 5.5 and we would like to to create a custom search > form on DSpace homepage, allowing us to use advanced filters together with > search query in a similar fashion as it is possible on Discovery page (e.g. > https://dspace.cuni.cz/discover). Is it possible to add a custom search > field together with advanced filters? > > The idea is to have a search field at the top of the homepage, followed by > list of communities. So far I was able to just add a simple search field > without any additional filtering options (https://dspace.cuni.cz) by > modifying news-xmlui.xml file: > > interactive="yes" rend="primary" action="/discover" n="front-page-search" > method="get"> > Search DSpace > Enter some text in the box below to search DSpace. > > type="text"> > type="button"> Go > > > > (it is an example code I got from > http://wiki.lib.sun.ac.za/index.php?title=SUNScholar/XMLUI_Theme/M1/Page_Structure > ) > Our Dspace installation details: > > * DSpace version*: 5.5 > *UI*: XMLUI / Mirage 2 theme > > Thank you in advance, > best regards, > > Jakub Řihák > > Charles University > Czech Republic > > > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/95439e40-2f19-4ffc-9adc-dc8469320987%40googlegroups.com.
[dspace-tech] Hierarchical (taxonomies based) sidebar facets not work?
Hi all, I've just tried to configure Hierarchical (taxonomies based) sidebar facets in DSpace 6.2 (JSPUI) and I'm not sure if it works OK or not, because the result looks a bit weird. My configuration in config/spring/api/discovery.xml is left default. There're two items in the collection, both have dc.subject, the first one: dc.subject = MATEMATIKA::ALGEBRA::LINEARNIALGEBRA dc.subject = MATEMATIKA::ALGEBRA::GRUPY See the result in the attachment. Is it intended result? What if the taxonomy tree is larger and deeper? It won't be very nice then I guess. Regards, Vlastik -- Mgr. Vlastimil Krejčíř Library and Information Centre, Institute of Computer Science Masaryk University, Brno, Czech Republic Email: krejcir (at) ics (dot) muni (dot) cz Phone: +420 549 49 3872 OpenPGP key: https://kic-internal.ics.muni.cz/~krejvl/pgp/ Fingerprint: 7800 64B2 6E20 645B 56AF C303 34CB 1495 C641 11B9 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/1a41b39a-8cfe-9428-d0fd-2a070348ac81%40ics.muni.cz.
[dspace-tech] Published Item back to WorkflowItem
Hi all, I've been recently asked whether it is possible to move published item to the workflow process. Once the new Item is published you can edit the metadata only in a simple DC form. This is not very user friendly. Is it possible to move a published Item back to the workflow process and edit metadata via the forms configured by the input_forms.xml? Regards, Vlastik -- Vlastimil Krejčíř Library and Information Centre, Institute of Computer Science Masaryk University, Brno, Czech Republic Email: krejcir (at) ics (dot) muni (dot) cz Phone: +420 549 49 3872 OpenPGP key: https://kic-internal.ics.muni.cz/~krejvl/pgp/ Fingerprint: 7800 64B2 6E20 645B 56AF C303 34CB 1495 C641 11B9 -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e7cfcb87-a93a-2c6d-0906-1260b1dfd916%40ics.muni.cz.
Re: [dspace-tech] Multitenancy / multisite DSpace
Hello Paul, thank you for your answer. I saw your presentation at OR - yes, you are right, this kind of automation is the way. However, in case I have small projects, the multitenancy makes still sense. For example we are just helping our archeologists to preserve the data for the artifacts they collected at certain locality, just only about 300 items. There won't be more in this project (since they probably will not find anything more there). In such case the scalability would be OK (the target audience is quite small). Having just the assetstore in case of serious breakdown (I would say disaster :-)) could be a trouble, but having also the database and related things backup... Nevertheless, you are right, it is a risk. Regards, Vlastik On 8/14/19 7:41 AM, Paul Münch wrote: > Hello Vlastik, > > we run a handful DSpace instances at our institution. For every service > we have a single instance - independent of number of items. We discussed > your solution, too. But decided against, because of following points: > > * lesser scabalbility and maintenanability if there come more services > or users > * all data are in one assetstore unassigend to a service - in case of a > serious breakdown it could be very hard to separate the data and move > them consistent in an another system (DSpace or something else) > > For us it is the best way to install and maintain one instance for one > service. If there are only less items, your single VM don't need that > much power, too. > > I'm not sure, if you maybe talked to my colleague. But we introduced at > OR2019 our DSpace-Clustering > (https://www.conftool.net/or2019/index.php?page=browseSessions_session=349). > Maybe the setup is interesting for you - besides the Puppet > configuration. At our institution we run both all components on a single > VM and each component on a single VM (Clustering). > > Kind regards, > > Paul Münch > > Am 13.08.19 um 17:00 schrieb Vlastimil Krejčíř: >> Hi all, >> >> I would like to ask/discuss a (probably?) new topic - a >> multitenancy/multisite DSpace. What exactly do I mean? >> >> I want to have several projects in one instance of DSpace. For example >> the archive of mathematics and the archive for archeologists. Both are >> rather small (hundreds or small thousands of Items), but different >> metadata, different structures). Or another example is to provide the >> archives for two different institutions. (Yes, I can install two >> DSpace instances, with help of Puppets, Docker and such tools, >> however, especially in case of small projects it makes sense to have >> just only one instance of DSpace.) >> >> I would like to achieve absolute transparency to end users: >> >> 1. both project have separate URLs >> 2. different web design >> 3. separate data for browse and search >> 4. different metadata schemas (or just metadata fields) >> 5. separate handles (prefixes) >> 6. separate administration >> >> >> I have thought about this points and my guess is that I can simulate >> the projects via communities (one project = one community): >> >> 1. possible using mod_rewrite (somehow, I haven't thought of details) >> 2. definitely possible via XMLUI (not sure about Angular in DSpace 7) >> 3. possible using browse and search the community >> 4. possible >> 5. not possible (or need further development) >> 6. probably possible >> >> The question might be scalability, but I think it should be OK for >> smaller projects (lets say up to ten projects, each of them no more >> than thousands of Items). >> >> I discussed this topic with some of you at OR 2019 in Hamburg and I >> was redirected to this page: >> >> https://csufresno-dspace.calstate.edu/ >> >> which is probably something I want to achieve (just click the >> communities, the URL and design will change). >> >> Are there anyone in the community who has already tried to solve this? >> How do you technically solve for example the point no. 1 in my list? I >> would be really grateful if you could share you experience. >> >> Regards, >> >> Vlastik >> >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code >> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google >> Groups "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to dspace-tech+unsubscr...@googlegroups.com >> <mailto:dspace-tech+unsubscr...@googlegroups.com>. >&g
[dspace-tech] Multitenancy / multisite DSpace
Hi all, I would like to ask/discuss a (probably?) new topic - a multitenancy/multisite DSpace. What exactly do I mean? I want to have several projects in one instance of DSpace. For example the archive of mathematics and the archive for archeologists. Both are rather small (hundreds or small thousands of Items), but different metadata, different structures). Or another example is to provide the archives for two different institutions. (Yes, I can install two DSpace instances, with help of Puppets, Docker and such tools, however, especially in case of small projects it makes sense to have just only one instance of DSpace.) I would like to achieve absolute transparency to end users: 1. both project have separate URLs 2. different web design 3. separate data for browse and search 4. different metadata schemas (or just metadata fields) 5. separate handles (prefixes) 6. separate administration I have thought about this points and my guess is that I can simulate the projects via communities (one project = one community): 1. possible using mod_rewrite (somehow, I haven't thought of details) 2. definitely possible via XMLUI (not sure about Angular in DSpace 7) 3. possible using browse and search the community 4. possible 5. not possible (or need further development) 6. probably possible The question might be scalability, but I think it should be OK for smaller projects (lets say up to ten projects, each of them no more than thousands of Items). I discussed this topic with some of you at OR 2019 in Hamburg and I was redirected to this page: https://csufresno-dspace.calstate.edu/ which is probably something I want to achieve (just click the communities, the URL and design will change). Are there anyone in the community who has already tried to solve this? How do you technically solve for example the point no. 1 in my list? I would be really grateful if you could share you experience. Regards, Vlastik -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/081375bd-9f45-428f-9084-901b599178cb%40googlegroups.com.
