Re: [dspace-tech] Compatibility Mirage2 DSpace 7
Thank you very much for your detailed reply Tim. El viernes, 14 de diciembre de 2018, 19:38:53 (UTC-3), Tim Donohue escribió: > > Hello Hernán, > > Unfortunately, existing themes from DSpace 6 (or below) will *not* be > compatible with DSpace 7. In DSpace 7 we've moved to an entirely new user > interface (based on Angular) and past themes from XMLUI or JSPUI cannot be > directly converted (as XMLUI based themes are XSLT based, and JSPUI themes > are JSP based, and neither of those technologies are compatible with > Angular). > > That said, obviously, you may be able to borrow HTML-level concepts from > DSpace 6 themes (e.g. CSS) and reapply them to DSpace 7. However, at this > time, since DSpace 7 is still in active development, it's hard to give any > more specifics on what might be possible here. > > - Tim > > On Fri, Dec 14, 2018 at 2:39 PM Hernán Lagos > wrote: > >> Hi All >> >> Does anyone know if themes based on Mirage2 will become obsolete in >> DSpace 7? >> >> Thanks >> >> -- >> 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...@googlegroups.com . >> To post to this group, send email to dspac...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
RE: [dspace-tech] REST api
Following up... The POST body requires a MetadataEntry object. More information here: DSpace 5.x: https://wiki.duraspace.org/display/DSDOC5x/REST+API#RESTAPI-Model-Objectdatatypes DSpace 6.x: https://wiki.duraspace.org/display/DSDOC6x/REST+API#RESTAPI-Model-Objectdatatypes -- Sean -Original Message- From: Sean Kalynuk Sent: December 17, 2018 1:39 PM To: 'Jose Blanco' ; DSpace Technical Support Subject: RE: [dspace-tech] REST api Hi Jose, Looks like there's a bug in 5.1: https://jira.duraspace.org/browse/DS-2501?src=confmacro Also, I think the find-by-metadata-field request requires a POST instead of a GET. Using GET might have resulted in the 405 error. -- Sean -Original Message- From: dspace-tech@googlegroups.com On Behalf Of Jose Blanco Sent: December 17, 2018 12:57 PM To: DSpace Technical Support Subject: [dspace-tech] REST api what is wrong with this request? RESTapi/items/find-by-metadata-field?key=dc.title=test=en_US I'm getting a 405 error. With dspace versin 5.1 Thank you! -Jose -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
RE: [dspace-tech] REST api
Hi Jose, Looks like there's a bug in 5.1: https://jira.duraspace.org/browse/DS-2501?src=confmacro Also, I think the find-by-metadata-field request requires a POST instead of a GET. Using GET might have resulted in the 405 error. -- Sean -Original Message- From: dspace-tech@googlegroups.com On Behalf Of Jose Blanco Sent: December 17, 2018 12:57 PM To: DSpace Technical Support Subject: [dspace-tech] REST api what is wrong with this request? RESTapi/items/find-by-metadata-field?key=dc.title=test=en_US I'm getting a 405 error. With dspace versin 5.1 Thank you! -Jose -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] REST api
what is wrong with this request? RESTapi/items/find-by-metadata-field?key=dc.title=test=en_US I'm getting a 405 error. With dspace versin 5.1 Thank you! -Jose -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
Re: [dspace-tech] Problems with activating SWORDv2 Interface
Hello Matthias, the username for sword is a valid DSpace Eperson. Based on the submission rights the subsequent servicedocument is created. Hope this helps Claudia Jürgen Am 17.12.2018 um 12:12 schrieb Genzmehr, Matthias: Hi All, we are using Dspace 6.3 and want to activate the SWORDv2 Interface for connectivity to Symplectic Elements Software. The Tomact log file says that the module is deployed. All ohter modules (jspui, rest, oai ect.) do work fine. Swordv2 asks for a username and password. The request disappears by entering the Tomcat manager user and password but it results in a http 403 error. Can anyone help? Which user and password is required here? Is it a DSpace problem or a Tomcat configuration problem? Thanks a lot! Matthias Genzmehr -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 claudia.juer...@tu-dortmund.de www.ub.tu-dortmund.de Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax. -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] Problems with activating SWORDv2 Interface
Hi All, we are using Dspace 6.3 and want to activate the SWORDv2 Interface for connectivity to Symplectic Elements Software. The Tomact log file says that the module is deployed. All ohter modules (jspui, rest, oai ect.) do work fine. Swordv2 asks for a username and password. The request disappears by entering the Tomcat manager user and password but it results in a http 403 error. Can anyone help? Which user and password is required here? Is it a DSpace problem or a Tomcat configuration problem? Thanks a lot! Matthias Genzmehr -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
[dspace-tech] RE: Setting Embargo terms via metadata
Hello again, Just coming back to inform anyone who might be interested that I managed to assign the date I need, automatically during the submission process. I selected a different embargo setter: DayTableEmbargoSetter and mapped 3 years to 1095 days in local.cfg : embargo.terms.days = 3 years:1095 Hope someone finds it useful. Best regards, Kiriaki From: Kiriaki Roditi Sent: Tuesday, November 20, 2018 1:12 PM To: dspace-tech@googlegroups.com Subject: Setting Embargo terms via metadata Hello everyone, I am trying to configure Embargo via metadata terms and set the embargo liftDate to 3 years after the item was installed in the Repository. I have configured the appropriate metadata field and created a list of metadata values in input-forms.xml but I cannot set the date I need in the liftDate metadata field. Is there a way to achieve that in DSpace 6.3 (Mirage2 interface)? Thank you in advance. Best regards, Kiriaki -- 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 post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
