[dspace-tech] SQL query to Insert value to a field based from another field if it doesn't exisst
Dear SQL experts, I am planning to insert value to a field if and only if it doesn't exist. For example, there are items that have the entry 'Hypophthalmichthys nobilis' in the dc.subject field. I would like to duplicate this entry to another new field dc.subject.scientificName. I have issued this SQL query to list the items in the dc.subject containing 'Hypophthalmichthys nobilis": select distinct dspace_object_id, metadata_field_id, text_value, authority, confidence from metadatavalue where metadata_field_id=57 and text_value='Hypophthalmichthys nobilis' [image: Capture.PNG] I wonder what would be the SQL query to insert 'Hypophthalmichthys nobilis' found in dc.subject with metadata_field_id=57 to another field dc.subject.scientificName with metadata_field_id=155 if it doesn't exist yet? My example above is only 4 items but I have hundreds of items to that I need to update also. Previously, my method is to export the metadata containing the field I want to insert, batch edit the CSV, import it, and then do the SQL update, which is quite tedious especially during the batch edit because dc.subject contains other terms separated by double pipes (||). I thought there must be an easier way to do this via SQL. DSpace version is 6.3 by the way. Thanks in advance and best regards, euler -- 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/41138f8d-5d95-4e27-a4ca-c9b6e154e1aan%40googlegroups.com.
[dspace-tech] Re: DSpace 7 docker images with M1 Mac
So apparently maven and tomcat have arm64 builds. Adding --platform=linux/arm64/v8 to Dockerfile.dependencies like this FROM --platform=linux/arm64/v8 maven:3-jdk-11 as build I locally built this dependency image and used that as a base for the build in Dockerfile.test and Dockerfile.cli, like so FROM --platform=linux/arm64/v8 anis/dspace-dep:latest as build I also added the same line into the ant deploy and run tomcat section, like this FROM --platform=linux/arm64/v8 tomcat:9-jdk11 So the build is working now! I can look into if this multiarch support is easy to integrate to DSpace images and their deployments. On Friday, January 21, 2022 at 4:09:16 PM UTC Anis wrote: > Hi, and thanks for the quick reply! > > The versioning seems to be super confusing, but I think that Server VM > 18.9 is the server VM of java 11. > > Digging through some answers it seems that the base openjdk image is > incompatible with ARM-architechture, not 100% sure though, so I will keep > digging. > > - Anis > > On Friday, January 21, 2022 at 3:30:06 PM UTC Tim Donohue wrote: > >> Hi Anis, >> >> It appears, from that stacktrace, that you might somehow be using OpenJDK >> v18? The DSpace 7 backend will only currently build on OpenJDK v11 >> (though we will have v17 support coming soon in 7.2 via this PR >> https://github.com/DSpace/DSpace/pull/8104). >> >> I don't have a Mac to test things on, but this *might* be related to the >> Segfault? Or it could be entirely unrelated, I don't know. It's just what >> immediately jumped out at me. >> >> Tim >> >> On Friday, January 21, 2022 at 9:09:05 AM UTC-6 Anis wrote: >> >>> Hello! >>> >>> I've recently moved to a new laptop with the new M1 chip and tried to do >>> a docker build on the DSpace 7 images, but it fails to a segfault. I'm >>> wondering if anyone else has got the build working on these new chips? I'm >>> using Docker Desktop for Apple chips, I don't know if switching back to the >>> Intel one and emulating would be a working solution. >>> >>> I ran the following command >>> docker-compose -f docker-compose.yml -f docker-compose-cli.yml build >>> >>> and got the following stack trace >>> >>> #23 31.91 [INFO] --- maven-compiler-plugin:3.8.1:compile >>> (default-compile) @ dspace-services --- >>> #23 35.02 [INFO] Changes detected - recompiling the module! >>> #23 35.04 [INFO] Compiling 80 source files to >>> /app/dspace-services/target/classes >>> #23 54.93 # >>> #23 54.93 # A fatal error has been detected by the Java Runtime >>> Environment: >>> #23 54.93 # >>> #23 54.93 # SIGSEGV (0xb) at pc=0xe2ffba39, pid=11, tid=50 >>> #23 54.93 # >>> #23 54.93 # JRE version: OpenJDK Runtime Environment 18.9 (11.0.13+8) >>> (build 11.0.13+8) >>> #23 54.93 # Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.13+8, mixed >>> mode, sharing, tiered, compressed oops, g1 gc, linux-amd64) >>> #23 54.93 # Problematic frame: >>> #23 54.93 # C 0xe2ffba39 >>> #23 54.93 # >>> #23 54.93 # No core dump will be written. Core dumps have been disabled. >>> To enable core dumping, try "ulimit -c unlimited" before starting Java again >>> #23 54.93 # >>> #23 54.93 # An error report file with more information is saved as: >>> #23 54.93 # /app/hs_err_pid11.log >>> #23 54.94 Compiled method (c1) 54521 9406 ! 2 >>> com.sun.tools.javac.file.PathFileObject::getLastModified (18 bytes) >>> #23 54.95 total in heap [0x0040161bdc10,0x0040161be2d0] = 1728 >>> #23 54.95 relocation [0x0040161bdd88,0x0040161bddf8] = 112 >>> #23 54.95 main code [0x0040161bde00,0x0040161be060] = 608 >>> #23 54.95 stub code [0x0040161be060,0x0040161be0e0] = 128 >>> #23 54.95 oops [0x0040161be0e0,0x0040161be0f0] = 16 >>> #23 54.95 metadata [0x0040161be0f0,0x0040161be110] = 32 >>> #23 54.95 scopes data[0x0040161be110,0x0040161be170] = 96 >>> #23 54.95 scopes pcs [0x0040161be170,0x0040161be210] = 160 >>> #23 54.95 dependencies [0x0040161be210,0x0040161be218] = 8 >>> #23 54.95 handler table [0x0040161be218,0x0040161be2c0] = 168 >>> #23 54.95 nul chk table [0x0040161be2c0,0x0040161be2d0] = 16 >>> #23 54.95 Compiled method (c2) 54529 9444 4 >>> com.sun.tools.javac.code.Types$12::visitClassType (10 bytes) >>> #23 54.95 total in heap [0x00401c6aac10,0x00401c6abce8] = 4312 >>> #23 54.95 relocation [0x00401c6aad88,0x00401c6aae30] = 168 >>> #23 54.95 main code [0x00401c6aae40,0x00401c6ab540] = 1792 >>> #23 54.95 stub code [0x00401c6ab540,0x00401c6ab568] = 40 >>> #23 54.95 oops [0x00401c6ab568,0x00401c6ab588] = 32 >>> #23 54.95 metadata [0x00401c6ab588,0x00401c6ab608] = 128 >>> #23 54.95 scopes data[0x00401c6ab608,0x00401c6ab8d0] = 712 >>> #23 54.95 scopes pcs [0x00401c6ab8d0,0x00401c6abb60] = 656 >>> #23 54.95 dependencies
[dspace-tech] Re: DSpace 7 docker images with M1 Mac
Hi, and thanks for the quick reply!
The versioning seems to be super confusing, but I think that Server VM 18.9
is the server VM of java 11.
Digging through some answers it seems that the base openjdk image is
incompatible with ARM-architechture, not 100% sure though, so I will keep
digging.
- Anis
On Friday, January 21, 2022 at 3:30:06 PM UTC Tim Donohue wrote:
> Hi Anis,
>
> It appears, from that stacktrace, that you might somehow be using OpenJDK
> v18? The DSpace 7 backend will only currently build on OpenJDK v11
> (though we will have v17 support coming soon in 7.2 via this PR
> https://github.com/DSpace/DSpace/pull/8104).
>
> I don't have a Mac to test things on, but this *might* be related to the
> Segfault? Or it could be entirely unrelated, I don't know. It's just what
> immediately jumped out at me.
>
> Tim
>
> On Friday, January 21, 2022 at 9:09:05 AM UTC-6 Anis wrote:
>
>> Hello!
>>
>> I've recently moved to a new laptop with the new M1 chip and tried to do
>> a docker build on the DSpace 7 images, but it fails to a segfault. I'm
>> wondering if anyone else has got the build working on these new chips? I'm
>> using Docker Desktop for Apple chips, I don't know if switching back to the
>> Intel one and emulating would be a working solution.
>>
>> I ran the following command
>> docker-compose -f docker-compose.yml -f docker-compose-cli.yml build
>>
>> and got the following stack trace
>>
>> #23 31.91 [INFO] --- maven-compiler-plugin:3.8.1:compile
>> (default-compile) @ dspace-services ---
>> #23 35.02 [INFO] Changes detected - recompiling the module!
>> #23 35.04 [INFO] Compiling 80 source files to
>> /app/dspace-services/target/classes
>> #23 54.93 #
>> #23 54.93 # A fatal error has been detected by the Java Runtime
>> Environment:
>> #23 54.93 #
>> #23 54.93 # SIGSEGV (0xb) at pc=0xe2ffba39, pid=11, tid=50
>> #23 54.93 #
>> #23 54.93 # JRE version: OpenJDK Runtime Environment 18.9 (11.0.13+8)
>> (build 11.0.13+8)
>> #23 54.93 # Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.13+8, mixed
>> mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
>> #23 54.93 # Problematic frame:
>> #23 54.93 # C 0xe2ffba39
>> #23 54.93 #
>> #23 54.93 # No core dump will be written. Core dumps have been disabled.
>> To enable core dumping, try "ulimit -c unlimited" before starting Java again
>> #23 54.93 #
>> #23 54.93 # An error report file with more information is saved as:
>> #23 54.93 # /app/hs_err_pid11.log
>> #23 54.94 Compiled method (c1) 54521 9406 ! 2
>> com.sun.tools.javac.file.PathFileObject::getLastModified (18 bytes)
>> #23 54.95 total in heap [0x0040161bdc10,0x0040161be2d0] = 1728
>> #23 54.95 relocation [0x0040161bdd88,0x0040161bddf8] = 112
>> #23 54.95 main code [0x0040161bde00,0x0040161be060] = 608
>> #23 54.95 stub code [0x0040161be060,0x0040161be0e0] = 128
>> #23 54.95 oops [0x0040161be0e0,0x0040161be0f0] = 16
>> #23 54.95 metadata [0x0040161be0f0,0x0040161be110] = 32
>> #23 54.95 scopes data[0x0040161be110,0x0040161be170] = 96
>> #23 54.95 scopes pcs [0x0040161be170,0x0040161be210] = 160
>> #23 54.95 dependencies [0x0040161be210,0x0040161be218] = 8
>> #23 54.95 handler table [0x0040161be218,0x0040161be2c0] = 168
>> #23 54.95 nul chk table [0x0040161be2c0,0x0040161be2d0] = 16
>> #23 54.95 Compiled method (c2) 54529 9444 4
>> com.sun.tools.javac.code.Types$12::visitClassType (10 bytes)
>> #23 54.95 total in heap [0x00401c6aac10,0x00401c6abce8] = 4312
>> #23 54.95 relocation [0x00401c6aad88,0x00401c6aae30] = 168
>> #23 54.95 main code [0x00401c6aae40,0x00401c6ab540] = 1792
>> #23 54.95 stub code [0x00401c6ab540,0x00401c6ab568] = 40
>> #23 54.95 oops [0x00401c6ab568,0x00401c6ab588] = 32
>> #23 54.95 metadata [0x00401c6ab588,0x00401c6ab608] = 128
>> #23 54.95 scopes data[0x00401c6ab608,0x00401c6ab8d0] = 712
>> #23 54.95 scopes pcs [0x00401c6ab8d0,0x00401c6abb60] = 656
>> #23 54.95 dependencies [0x00401c6abb60,0x00401c6abb70] = 16
>> #23 54.95 handler table [0x00401c6abb70,0x00401c6abc78] = 264
>> #23 54.95 nul chk table [0x00401c6abc78,0x00401c6abce8] = 112
>> #23 54.99 #
>> #23 54.99 # If you would like to submit a bug report, please visit:
>> #23 54.99 # https://bugreport.java.com/bugreport/crash.jsp
>> #23 54.99 #
>> #23 54.99 qemu: uncaught target signal 6 (Aborted) - core dumped
>> #23 55.04 Aborted
>> --
>> failed to solve: rpc error: code = Unknown desc = executor failed running
>> [/bin/sh -c mvn package -Pdspace-rest && mv
>> /app/dspace/target/${TARGET_DIR}/* /install && mvn clean]: exit code: 134
>>
>> thanks,
>>
>> - Anis
>>
>
--
All messages to this mailing list should adhere to the Code of Conduct:
[dspace-tech] Re: DSpace 7 docker images with M1 Mac
Hi Anis,
It appears, from that stacktrace, that you might somehow be using OpenJDK
v18? The DSpace 7 backend will only currently build on OpenJDK v11
(though we will have v17 support coming soon in 7.2 via this
PR https://github.com/DSpace/DSpace/pull/8104).
I don't have a Mac to test things on, but this *might* be related to the
Segfault? Or it could be entirely unrelated, I don't know. It's just what
immediately jumped out at me.
Tim
On Friday, January 21, 2022 at 9:09:05 AM UTC-6 Anis wrote:
> Hello!
>
> I've recently moved to a new laptop with the new M1 chip and tried to do a
> docker build on the DSpace 7 images, but it fails to a segfault. I'm
> wondering if anyone else has got the build working on these new chips? I'm
> using Docker Desktop for Apple chips, I don't know if switching back to the
> Intel one and emulating would be a working solution.
>
> I ran the following command
> docker-compose -f docker-compose.yml -f docker-compose-cli.yml build
>
> and got the following stack trace
>
> #23 31.91 [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile)
> @ dspace-services ---
> #23 35.02 [INFO] Changes detected - recompiling the module!
> #23 35.04 [INFO] Compiling 80 source files to
> /app/dspace-services/target/classes
> #23 54.93 #
> #23 54.93 # A fatal error has been detected by the Java Runtime
> Environment:
> #23 54.93 #
> #23 54.93 # SIGSEGV (0xb) at pc=0xe2ffba39, pid=11, tid=50
> #23 54.93 #
> #23 54.93 # JRE version: OpenJDK Runtime Environment 18.9 (11.0.13+8)
> (build 11.0.13+8)
> #23 54.93 # Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.13+8, mixed mode,
> sharing, tiered, compressed oops, g1 gc, linux-amd64)
> #23 54.93 # Problematic frame:
> #23 54.93 # C 0xe2ffba39
> #23 54.93 #
> #23 54.93 # No core dump will be written. Core dumps have been disabled.
> To enable core dumping, try "ulimit -c unlimited" before starting Java again
> #23 54.93 #
> #23 54.93 # An error report file with more information is saved as:
> #23 54.93 # /app/hs_err_pid11.log
> #23 54.94 Compiled method (c1) 54521 9406 ! 2
> com.sun.tools.javac.file.PathFileObject::getLastModified (18 bytes)
> #23 54.95 total in heap [0x0040161bdc10,0x0040161be2d0] = 1728
> #23 54.95 relocation [0x0040161bdd88,0x0040161bddf8] = 112
> #23 54.95 main code [0x0040161bde00,0x0040161be060] = 608
> #23 54.95 stub code [0x0040161be060,0x0040161be0e0] = 128
> #23 54.95 oops [0x0040161be0e0,0x0040161be0f0] = 16
> #23 54.95 metadata [0x0040161be0f0,0x0040161be110] = 32
> #23 54.95 scopes data[0x0040161be110,0x0040161be170] = 96
> #23 54.95 scopes pcs [0x0040161be170,0x0040161be210] = 160
> #23 54.95 dependencies [0x0040161be210,0x0040161be218] = 8
> #23 54.95 handler table [0x0040161be218,0x0040161be2c0] = 168
> #23 54.95 nul chk table [0x0040161be2c0,0x0040161be2d0] = 16
> #23 54.95 Compiled method (c2) 54529 9444 4
> com.sun.tools.javac.code.Types$12::visitClassType (10 bytes)
> #23 54.95 total in heap [0x00401c6aac10,0x00401c6abce8] = 4312
> #23 54.95 relocation [0x00401c6aad88,0x00401c6aae30] = 168
> #23 54.95 main code [0x00401c6aae40,0x00401c6ab540] = 1792
> #23 54.95 stub code [0x00401c6ab540,0x00401c6ab568] = 40
> #23 54.95 oops [0x00401c6ab568,0x00401c6ab588] = 32
> #23 54.95 metadata [0x00401c6ab588,0x00401c6ab608] = 128
> #23 54.95 scopes data[0x00401c6ab608,0x00401c6ab8d0] = 712
> #23 54.95 scopes pcs [0x00401c6ab8d0,0x00401c6abb60] = 656
> #23 54.95 dependencies [0x00401c6abb60,0x00401c6abb70] = 16
> #23 54.95 handler table [0x00401c6abb70,0x00401c6abc78] = 264
> #23 54.95 nul chk table [0x00401c6abc78,0x00401c6abce8] = 112
> #23 54.99 #
> #23 54.99 # If you would like to submit a bug report, please visit:
> #23 54.99 # https://bugreport.java.com/bugreport/crash.jsp
> #23 54.99 #
> #23 54.99 qemu: uncaught target signal 6 (Aborted) - core dumped
> #23 55.04 Aborted
> --
> failed to solve: rpc error: code = Unknown desc = executor failed running
> [/bin/sh -c mvn package -Pdspace-rest && mv
> /app/dspace/target/${TARGET_DIR}/* /install && mvn clean]: exit code: 134
>
> thanks,
>
> - Anis
>
--
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/0c3497f3-22ff-49f7-9878-4077b29b2d69n%40googlegroups.com.
[dspace-tech] Re: Custom material internal id
Hi, You have not provided any information about what version of DSpace you are using. However, I'll guess it may be DSpace 6.x... In any case, most DSpace releases include an "update-sequences.sql" script which can "reset/correct" any of these ID problems. Usually it's under your installation folder [dspace]/etc/postgres/update-sequences.sql ... however in 7.x it's available from the "dspace" commandline script (./dspace update-sequences). In the future, please send more information about the version of DSpace you are using, so that we are able to provide more specific help. See our Support guide for more info: https://wiki.lyrasis.org/display/DSPACE/Support Tim On Friday, January 21, 2022 at 7:00:11 AM UTC-6 Vlad wrote: > Hello colleagues! > After restoring the database, we needed to change the initial material > identifier that is generated by dspace when creating a new material. For > example, if we add a new material, it gets an id starting from 1382 ( > http://ourrepository.edu/handle/123456789/1382). How can I make it so > that the id continues, for example, with "5000" ( > http://ourrepository.edu/handle/123456789/5000) ? Thanks for any answer! > -- 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/30d522ec-cdc3-415a-b98f-3f8dd8162e5an%40googlegroups.com.
[dspace-tech] Re: frontend installation error
See the guide here for finding the underlying error that is causing your
DSpace user interface not to
load.
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
Unfortunately, there are a variety of reasons why the UI might not be able
to communicate with the backend, so you have to find the underlying error
message to determine which scenario you are encountering. It almost always
is a configuration problem, but it may be a configuration issue on the
frontend or on the backend. See also this list of "common issues" most of
which can result in the UI being unable to
load:
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
Once you find the underlying error message, if you cannot find it listed in
the Common Installation Issues, you can send it to this mailing list and we
can help.
Tim
On Thursday, January 20, 2022 at 10:34:11 AM UTC-6 alo...@gmail.com wrote:
> It's a common issue caused by how you setup DSpace. localhost usually
> configured if you can access this URL locally or using a tunneled
> connection for development/testing purposes.
>
> Stackoverflow poster is using Windows server 2012. Are you using Windows?
> or Linux?.
>
> On Thursday, January 20, 2022 at 3:49:18 PM UTC+3 ayatr...@gmail.com
> wrote:
>
>> hello
>> for a few days now i am having a problem in frontend installation just
>> like what is mentioned here
>> https://stackoverflow.com/questions/68811629/dspace-does-not-load
>>
>> my environment settings are
>> export const environment = {
>> // The "ui" section defines where you want Node.js to run/respond. It
>> often is a *localhost* (non-public) URL, especially if you are using a
>> Proxy.
>> // In this example, we are setting up our UI to just use localhost,
>> port 4000.
>> // This is a common setup for when you want to use Apache or Nginx to
>> handle HTTPS and proxy requests to Node on port 4000
>> ui: {
>> ssl: false,
>> host: 'localhost',
>> port: 4000,
>> // NOTE: Space is capitalized because 'namespace' is a reserved
>> string in TypeScript
>> nameSpace: '/'
>> },
>> // This example is valid if your Backend is publicly available at
>> https://api.mydspace.edu/server/
>> // The REST settings MUST correspond to the primary URL of the
>> backend. Usually, this means they must be kept in sync
>> // with the value of "dspace.server.url" in the backend's local.cfg
>> rest: {
>> ssl: false,
>> host: 'localhost',
>> port: 8080,
>> // NOTE: Space is capitalized because 'namespace' is a reserved
>> string in TypeScript
>> nameSpace: '/server'
>> }
>> };
>>
>> and when i try
>> yarn config:check:rest
>> the response is 200
>>
>> i tried to reinstall every thing and it did not work either .
>> can some one help me please
>>
>
--
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/af76516e-c69f-41ce-b39d-fadb59b4b83an%40googlegroups.com.
[dspace-tech] Re: HOW TO ENABLE LOGIN BY LDAP ACCOUNT - DSPACE 7
Hi Giang, LDAP authentication in DSpace uses the same login box as the PasswordAuthentication. So, it does not provide a separate button. Instead, to login via LDAP you should enter your LDAP login & password into the "Email address" and "Password" fields displayed in that form, and click "Log in". This is similar to the behavior that existed in DSpace 6 with regards to LDAP. LDAP uses the built in login form, while some other authentication plugins (like Shibboleth or similar) will have a button that sends you to an external system to login. Tim On Thursday, January 20, 2022 at 4:01:13 AM UTC-6 giang.tr...@gmail.com wrote: > Hello Every One, > > Are there any body has configured successful login to dspace-7 by ldap > account. > I have configured into *authentication.cfg* as below: > plugin.sequence.org.dspace.authenticate.AuthenticationMethod = > org.dspace.authenticate.PasswordAuthentication > plugin.sequence.org.dspace.authenticate.AuthenticationMethod = > org.dspace.authenticate.LDAPAuthentication > plugin.sequence.org.dspace.authenticate.AuthenticationMethod = > org.dspace.authenticate.OrcidAuthentication > > Afterthat, I have enabled into authentication-ldap.cfg as below: > authentication-ldap.enable = true > authentication-ldap.autoregister = true > authentication-ldap.provider_url = ldap://192.168.66.68:636/ > authentication-ldap.id_field = SamAccountName > and there are some others thing.. > > And the UI render only Login with ORCID ID button, and it doesn't display > login with ldap buttons. I have tried with shibboleth and UI also render > login with Shibboleth. Except login with ldap button. Are there any one has > been configure success dspace 7 or dspace cris 7 with LDAP can give me some > advice about this case. > [image: LDAP.JPG] > > Thank you very much. > Regards > Giang > -- 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/adfa3066-23e1-478e-9689-96866050e877n%40googlegroups.com.
[dspace-tech] DSpace 7 docker images with M1 Mac
Hello!
I've recently moved to a new laptop with the new M1 chip and tried to do a
docker build on the DSpace 7 images, but it fails to a segfault. I'm
wondering if anyone else has got the build working on these new chips? I'm
using Docker Desktop for Apple chips, I don't know if switching back to the
Intel one and emulating would be a working solution.
I ran the following command
docker-compose -f docker-compose.yml -f docker-compose-cli.yml build
and got the following stack trace
#23 31.91 [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile)
@ dspace-services ---
#23 35.02 [INFO] Changes detected - recompiling the module!
#23 35.04 [INFO] Compiling 80 source files to
/app/dspace-services/target/classes
#23 54.93 #
#23 54.93 # A fatal error has been detected by the Java Runtime Environment:
#23 54.93 #
#23 54.93 # SIGSEGV (0xb) at pc=0xe2ffba39, pid=11, tid=50
#23 54.93 #
#23 54.93 # JRE version: OpenJDK Runtime Environment 18.9 (11.0.13+8)
(build 11.0.13+8)
#23 54.93 # Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.13+8, mixed mode,
sharing, tiered, compressed oops, g1 gc, linux-amd64)
#23 54.93 # Problematic frame:
#23 54.93 # C 0xe2ffba39
#23 54.93 #
#23 54.93 # No core dump will be written. Core dumps have been disabled. To
enable core dumping, try "ulimit -c unlimited" before starting Java again
#23 54.93 #
#23 54.93 # An error report file with more information is saved as:
#23 54.93 # /app/hs_err_pid11.log
#23 54.94 Compiled method (c1) 54521 9406 ! 2
com.sun.tools.javac.file.PathFileObject::getLastModified (18 bytes)
#23 54.95 total in heap [0x0040161bdc10,0x0040161be2d0] = 1728
#23 54.95 relocation [0x0040161bdd88,0x0040161bddf8] = 112
#23 54.95 main code [0x0040161bde00,0x0040161be060] = 608
#23 54.95 stub code [0x0040161be060,0x0040161be0e0] = 128
#23 54.95 oops [0x0040161be0e0,0x0040161be0f0] = 16
#23 54.95 metadata [0x0040161be0f0,0x0040161be110] = 32
#23 54.95 scopes data[0x0040161be110,0x0040161be170] = 96
#23 54.95 scopes pcs [0x0040161be170,0x0040161be210] = 160
#23 54.95 dependencies [0x0040161be210,0x0040161be218] = 8
#23 54.95 handler table [0x0040161be218,0x0040161be2c0] = 168
#23 54.95 nul chk table [0x0040161be2c0,0x0040161be2d0] = 16
#23 54.95 Compiled method (c2) 54529 9444 4
com.sun.tools.javac.code.Types$12::visitClassType (10 bytes)
#23 54.95 total in heap [0x00401c6aac10,0x00401c6abce8] = 4312
#23 54.95 relocation [0x00401c6aad88,0x00401c6aae30] = 168
#23 54.95 main code [0x00401c6aae40,0x00401c6ab540] = 1792
#23 54.95 stub code [0x00401c6ab540,0x00401c6ab568] = 40
#23 54.95 oops [0x00401c6ab568,0x00401c6ab588] = 32
#23 54.95 metadata [0x00401c6ab588,0x00401c6ab608] = 128
#23 54.95 scopes data[0x00401c6ab608,0x00401c6ab8d0] = 712
#23 54.95 scopes pcs [0x00401c6ab8d0,0x00401c6abb60] = 656
#23 54.95 dependencies [0x00401c6abb60,0x00401c6abb70] = 16
#23 54.95 handler table [0x00401c6abb70,0x00401c6abc78] = 264
#23 54.95 nul chk table [0x00401c6abc78,0x00401c6abce8] = 112
#23 54.99 #
#23 54.99 # If you would like to submit a bug report, please visit:
#23 54.99 # https://bugreport.java.com/bugreport/crash.jsp
#23 54.99 #
#23 54.99 qemu: uncaught target signal 6 (Aborted) - core dumped
#23 55.04 Aborted
--
failed to solve: rpc error: code = Unknown desc = executor failed running
[/bin/sh -c mvn package -Pdspace-rest && mv
/app/dspace/target/${TARGET_DIR}/* /install && mvn clean]: exit code: 134
thanks,
- Anis
--
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/9d3b168a-0934-454d-b9ea-2386248a1926n%40googlegroups.com.
[dspace-tech] Records with a dc.contributor.author w/ dspace generated uid authority key not displayed in collection
Hello, system characteristics: DSpace 5.5, XMLUI *Situation*: Records with an author w/ dspace generated uid authority key are not displayed in collection. In an example collection, 10 records are listed, but actually 41 records exist. If I do a metadata export, records with dc.contributor.author (that have a uid authority key with a value like Surname, Name::d141b689-acec-4c97-a726-d4b9c651a805::600) are not listed when viewing the collection. I did an index-discovery -b and that did not fix it. I am wondering if this is a configuration issue. Has anyone faced this before? Thank you, Evelthon -- 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/a8d4fe3f-9781-4b7b-9929-39f12f0bd1een%40googlegroups.com.
[dspace-tech] Custom material internal id
Hello colleagues! After restoring the database, we needed to change the initial material identifier that is generated by dspace when creating a new material. For example, if we add a new material, it gets an id starting from 1382 (http://ourrepository.edu/handle/123456789/1382). How can I make it so that the id continues, for example, with "5000" (http://ourrepository.edu/handle/123456789/5000) ? Thanks for any answer! -- 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/f7bbecde-3e11-40af-89ed-611cb2ca7c14n%40googlegroups.com.
