[dspace-tech] Re: DOI import error when DOI contains parentheses. Publisher, the American Society of Civil Engineer
Recently I was doing work with APIs and I ran across the documents for the Crossref REST API at https://github.com/CrossRef/rest-api-doc. This includes the following warning: "You should always url-encode DOIs and parameter values when using the API. DOIs are notorious for including characters that break URLs (e.g. semicolons, hashes, slashes, ampersands, question marks, etc.)." Parentheses can be encoded as %28 and %29. On Tuesday, June 4, 2019 at 2:07:20 PM UTC-4, Mr. B wrote: > > Hi there, > We've been experiencing some issues with the import publication details > using > DOI feature when the DOI contains parentheses. See for example > 10.1016/S2214-109X(16)30242-X, where multiple publications are found. > Parentheses are pretty rare in DOIs but there is one publisher, the > American > Society of Civil Engineers, that includes them in all publications, see for > ex: https://doi.org/10.1061/(ASCE)AE.1943-5568.342. > Any help would be appreciated!! > > -- 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/de40284c-65d5-4011-9d52-8b3f94b3a1e3%40googlegroups.com.
[dspace-tech] DOI import error when DOI contains parentheses. Publisher, the American Society of Civil Engineer
Hi there, We've been experiencing some issues with the import publication details using DOI feature when the DOI contains parentheses. See for example 10.1016/S2214-109X(16)30242-X, where multiple publications are found. Parentheses are pretty rare in DOIs but there is one publisher, the American Society of Civil Engineers, that includes them in all publications, see for ex: https://doi.org/10.1061/(ASCE)AE.1943-5568.342. Any help would be appreciated!! -- 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/43da925d-e5e9-4f7a-b1b0-b7731bf9b37b%40googlegroups.com.
[dspace-tech] Re: Build failure when using theme from bootswatch in Mirage2
I am curious about this, too. We are running DSpace 6.3 with a customized Mirage2 theme. I tried to rebuild it to incorporate changes to the community-filiator command, and the build failed while trying to rebuild the Mirage2 theme. I added the Maven filtering to pom.xml described below and the build was successful. So far it seems to look and function fine. But I am not a developer and would appreciate any assurance that the new build is o.k. Thanks, Glenn On Friday, August 31, 2018 at 4:28:04 AM UTC-5, euler wrote: > > Dear All, > > I'm trying to use a theme from bootswatch.com[1] but I am encountering > this error during mvn build: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-resources-plugin:2.7:copy-resources > (default) on project xmlui-mirage2: Mark invalid -> [Help 1]. I searched in > Google for this error and found a Jira issue[2] filed by Terry Brady but it > says that is already closed and fixed. I am running DSpace 6.3 and have no > problems in Mirage2 build. I tried to look for other solutions and found > this [3] Stackoverflow post. So I followed the solution from the top answer > and the error went away. > > So basically what I did was edit the [dspace-src]/pom.xml and change the > code from: > > > org.apache.maven.plugins > maven-resources-plugin > 2.7 > > into: > > org.apache.maven.plugins > maven-resources-plugin > 2.7 > > > org.apache.maven.shared > maven-filtering > 1.3 > > > > > > I would like to ask now if this the correct or best solution? Although the > build error went away and I now have the theme from bootswatch, I'm afraid > of the repercussions later on. I'm hoping Terry would shed light on this on > how to fix that build error without modifying the pom.xml file. > > Thanks in advance and best regards! > euler > > [1] https://bootswatch.com/ > [2] https://jira.duraspace.org/browse/DS-3312 > [3] https://stackoverflow.com/q/26281322/1919069 > > -- 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/4ba842c7-bb45-4268-8cc5-76ddc9137118%40googlegroups.com.
[dspace-tech] HTTPS not working with REST OAI SWORD
Hello All, We recently installed a SSL certificate on our instance of Dspace. Everything seems to work for via the web browser but when making connection via Elements using rest and sword, we get Internal Error 500 401 We're using Apache for the SSL and then forwarding to Tomcat. I've followed the outline provided at https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-UsingSSLonApacheHTTPDinfrontofTomcat(runningonports80and443) AJP 1.3 is defined in the tomcat server.xml AJP proxypass and proxypassreverse setup in virtualhost :443 and a Redirect permanent to https in virtualhost : 80 Security Constraint was enabled in webapps/rest/ What am I missing? Dspace version 6.3 Apache version 2.4.6 Tomcat version 7.x Thanks in advance for any assistance. Best, Chin -- 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/5c3f3557-cbe2-47f0-afdb-0c2a4d41c4ca%40googlegroups.com.
