[dspace-tech] DataCite metadata schema 4.5
Hi, DataCite has announced that it will no longer accept metadata in version 3 of the metadata schema from the end of 2024. We at The Library Code have updated the DataCite metadata schema in DSpace to version 4.5. This will be included in DSpace 8 and DSpace 7.6.2. We recommend that you adapt the file DIM2DataCite.xsl to your local metadata schemas. If you want to use the DataCite schema 4.5 before migrating to DSpace 8 or 7.6.2 (which is not released yet), you can find the source code as follow. - The code changes can be found here: https://lnkd.in/ecUFq-3X - The new Dim2DataCite.xsl can be found here: https://lnkd.in/eaAEmjux Best regards, Pascal -- The Library Code GmbH Pascal-Nicolas Becker https://www.the-library-code.de -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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/E9971B88-BC6C-4660-858A-95CEA7367D71%40the-library-code.de.
[dspace-tech] Re: Assigning DOIs automatically for a single community
Hi Gail, hi Hrafn, hi everyone on this list, Hrafn already provided the correct link to our pull request, thanks for that. Let me add a little bit of background. Kim Shepherd and I are working with The Library Code. The Library Code is a DSpace Service Provider and Certified DSpace Partner. The pull request is based on code that we developed with the support of Technische Informationsbibliothek and Technische Universität Hamburg. Our code does provide the possibility to restrict the assignment of DOIs based on the owning collection of items. It also offers possibilities to make this decision depending on the existence of certain metadata fields, depending on the value of metadata fields, the existence of file(s) in certain Bundles, or many other questions. It is a complete filter system that allows to combine these rules with boolean logic (AND, OR, NOT). We will give a presentation at Open Repositories 2021 about that. To make it easy to apply upgrades to DSpace 5 and 6 those versions get bug fixes only and no new features, following the rules of the DSpace community. That is the reason we provided the pull request for DSpace 7 only. We do have code for DSpace 5 and DSpace 6 that is running in production at some of our clients. We do license this code as Open Source and are willing to make it publicly available, but we do need financial support to fund the work that we thing is still missing. We basically need to enhance our documentation and lower the effort needed to embed the code in DSpace installations. If anyone here is interested in getting the code for DSpace 5 and/or 6 and willing to help funding the necessary work, please get in touch with me. Best regards, Pascal hrafn.malmquist schrieb am Montag, 17. Mai 2021 um 14:37:04 UTC+2: > Hi Gail and other > > Sorry for the late reply. > > The implemention for 7.1 is advanced, and I know that a port to 6.x is > also very advanced. Kim Shepherd is doing this great work. See > https://github.com/DSpace/DSpace/pull/2789 > > The safe bet would be to wait for this feature to be officially > implemented. Although it is very unlikely that it will be included in the > upcoming 6.4 which we've been meaning to release for ages now. > > Alternatively, you could have a look at our workaround: > > https://github.com/UoEMainLibrary/DSpace-6.x/tree/doi_collection > > Note that this is a STATIC repo of a version of the 6.3 code. It is not in > sync with the live offical dspace-6_x branch. > > There are a few commits you would need on that branch, but the bulk of it > is in this one: > > https://github.com/UoEMainLibrary/DSpace-6.x/commit/70df2327bdff0515527f1178c3c8ee8874fbf599 > > > What this modification does is enable a checkbox in when editing a > collection (note, not when creating a new one) which, when checked, logs > the uuid of the collection in a new table in the database, doi_collection. > When the doi-organiser cronjob is run it will check if the item's owning > collection is in that table. This is then an on off switch for DOI minting > and mean you can submit an item with DOI minting off, switch it on and > submit an item that only gets a DOI. > > This might or might not cause a complication when migrating to a future > version of DSpace. Let me be clear, you can implement this at your own risk > with no guarantees. > > Best regards, Hrafn Malmquist > developer in the Digital Library Team, University of Edinburgh > > > -- > *From:* dspac...@googlegroups.com on behalf > of Sean Kalynuk > *Sent:* 10 May 2021 20:10 > *To:* Gail Steinhart ; dspac...@googlegroups.com < > dspac...@googlegroups.com> > *Subject:* [dspace-tech] Re: Assigning DOIs automatically for a single > community > > This email was sent to you by someone outside the University. > You should only click on links or attachments if you are certain that the > email is genuine and the content is safe. > > Hi Gail, > > > > There is a feature request for that functionality in DSpace 7, although it > doesn’t look like it has been implemented yet: > > > > https://jira.lyrasis.org/browse/DS-3749 > > > > As far as I can tell, DSpace 6 has DOI assignment for the whole > repository, or nothing at all. > > > > -- > > Sean > > > > *From: *dspac...@googlegroups.com on behalf > of Gail Steinhart > *Date: *Monday, May 10, 2021 at 1:56 PM > *To: *dspac...@googlegroups.com > *Subject: *[dspace-tech] Assigning DOIs automatically for a single > community > > *Caution:* This message was sent from outside the University of Manitoba. > > Greetings all and with apologies for posting to both lists. > > > > We have a use case where a community would like DOIs assigned to items in > all their collections automatically, but we do not want to do that across > the entire repository. Does anyone know if this is possible, and better > still, is anyone actually doing it? DSpace documentation is written for > implementation a
Re: [dspace-tech] XMLUI/Mirage 2: Community/Collection description as security issue
Hi Paul, this issue was discussed several times. Community/Collection descriptions can be edited by repository administrators and Community/Collection administrators only. We always said that those are trusted. Of course you can argue, that they could make mistakes even if they don’t want to, but it would be very hard to create a system that actively protects administrators from making any mistake. If we still feel the urge to change this, I would recommend to make it configurable, to allow the old behavior. Best regards, Pascal > Am 27.05.2020 um 14:54 schrieb Bram Luyten : > > Hi Paul, > > I definitely agree that it is a potential security risk and that people > editing community and collection pages have to watch out what they are doing. > However, the ability to get script tags executed on those pages makes some > integrations relatively light weight. > > One example are the Twitter badges you can configure via > https://publish.twitter.com/ > Copy paste the resulting script tag in your collection or community > description and the tweets are immediately there: > https://newdemo.openrepository.com/handle/2384/582855 > > Maybe it would make sense to allow or disallow either the entry of such code > into the description fields, or the rendering, based on a repository wide > on-off switch? > > with kindest regards, > > Bram > > Bram Luyten > 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 > Gaston Geenslaan 14, 3001 Leuven, Belgium > DSpace Express Hosting - Open Repository Hosting - Custom DSpace Services > > > On Wed, 27 May 2020 at 11:17, Paul Münch wrote: > Hello Mark, > > thanks for the reply. I checked the SimpleHTMLFragment.java, but it > isn't used in the community or collection UI. I guess that it's a XSLT > problem. > > HTML-code snippets in the community or collection description fields are > interpreted, but not on the item page. The only difference I see is that > in item-view.xsl the function xsl:value-of is used instead of > xsl:copy-of in community-view.xsl or collection-view.xsl. I update > xsl:copy-of to xsl:value-of but nothing changed. > > I like the feature it self but try to avoid users to add script-tags in > description texts. > > Kind regards, > > Paul Münch > > Am 19.05.20 um 14:56 schrieb Mark H. Wood: > > On Tue, May 19, 2020 at 08:09:07AM +0200, Paul Münch wrote: > >> unfortunately it is possible to add some executable scripts in the > >> description metadata of communities and collections. Even if someone don’t > >> plan evil things, inexperienced community or collection admins could do > >> some damage. > >> > >> Do you have a solution or a workaround for this? I've looked for the code > >> snippet which execute the HTML code but didn’t find anything. > > Have you looked at > > dspace-xmlui/src/main/java/org/dspace/app/xmlui/wing/element/SimpleHTMLFragment.java? > > > > -- > 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/cf549c62-255b-0010-45b3-8e1a94b4c978%40staff.uni-marburg.de. > > -- > 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/CACwo3X2q%2BrLP8ZPODaRLKv5cD_YMruTqMWCMEBZ2AFdJeqcg6g%40mail.gmail.com. -- The Library Code GmbH Pascal-Nicolas Becker Reichsstr. 18 14052 Berlin Germany pas...@the-library-code.de Tel.: +49 30 51 30 48 35 https://www.the-library-code.de Geschäftsführer: Pascal-Nicolas Becker Amtsgericht Charlottenburg, HRB 186457 B USt-IdNr.: DE311762726 -- 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/68EFFBB9-D002-4956-8A7F-510047F794A9%40the-library-code.de.
[dspace-tech] Call for participation: DSpace Anwendertreffen 2018
(German version below) The DSpace Anwendertreffen 2018 will take place at the university library of Technische Universität Berlin, on Thursday, 13th September 2018. It is organized by the university library of Technische Universität Berlin and The Library Code GmbH. This meeting is about informal exchange between DSpace users. After the success of the program structure last year, we kindly ask again for submissions in the format of talks and round tables. The idea of the round tables is to bring DSpace users together, to discuss one common topic. To give some examples: last year, round tables were offered about topics like duplicate detection, DSpace for newcomers, research data, and ORCID. We kindly ask you to send us proposals for both formats. If you would like to give a talk, please send us a short abstract including an estimation of the time your talk will take. If there is a topic you think a round table should discuss, please send us your idea. If you’re willing to offer a round table on a dedicated topic, please send us a short description. While the main conference language will be German, we will accept talks and round tables in English as well. Please send your proposals by email to anwendertref...@the-library-code.de within the deadline of June 17th, 2018. (Deutschsprachige Version) Das DSpace Anwendertreffen 2018 findet am Donnerstag, den 13. September 2018 an der Universitätsbibliothek der Technischen Universität Berlin statt. Es wird von der Universitätsbibliothek der Technischen Universität Berlin und The Library Code GmbH organisiert. Nach dem Erfolg der Programmstruktur im letzten Jahr bitten wir dieses Jahr wieder um Beiträge in Form von Vorträgen und Thementischen. Ein Thementisch soll DSpace-Anwender und -Anwenderinnen zusammenbringen, um ein gemeinsames Thema zu diskutieren. Letztes Jahr gab es zum Beispiel Thementische zu Themen wie Duplikatserkennung, DSpace für Einsteiger, Forschungsdaten und ORCID. Wir bitten Sie freundlich, uns Vorschläge für beide Formate zu schicken: Wenn Sie einen Vortrag halten möchten, senden Sie uns bitte eine kurze Zusammenfassung inklusive einer Angabe zum zeitlichen Rahmen Ihres Vortrags. Bitte senden Sie uns auch Themen, die Ihrer Meinung nach im Rahmen eines Thementisches behandelt werden sollen. Wenn Sie bereit sind, einen Tisch zu einem speziellen Thema anzubieten, senden Sie uns bitte eine kurze Beschreibung. Auch wenn die Konferenzsprache Deutsch ist, akzeptieren wir gerne auch Vorträge und Thementische in englischer Sprache. Bitte senden Sie uns Ihre Vorschläge per E-Mail ananwendertref...@the-library-code.de bis zum 17. Juni 2018. -- The Library Code GmbH Pascal-Nicolas Becker Reichsstr. 18 14052 Berlin Germany cont...@the-library-code.de Tel.: +49 30 51 30 48 35 https://www.the-library-code.de Geschäftsführer: Pascal-Nicolas Becker Amtsgericht Charlottenburg, HRB 186457 B USt-IdNr.: DE311762726 -- 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.
