[dspace-tech] Export Person Publications Error

2024-04-11 Thread Jack OE 
Hi all,
Whenever I Login and click Researchers → Publications → Export 
(Publication), I get a "There are no items to export with the selected 
configuration" error message when there are clearly items to export.

Not sure what could be causing the issue, can anyone help me out with this? 
Thanks

My Environment
dspaceVersion: "DSpace 7.6.1"
crisVersion: "cris-2023.02.03"

Use Docker
Traefik proxy → Angular → Dspace

Traefik proxy middleware setting
## Middlewares HTTP Headers - customHeader
- 
"traefik.http.middlewares.customHeader.headers.customFrameOptionsValue=SAMEORIGIN"
- "traefik.http.middlewares.customHeader.headers.contentTypeNosniff=true"
- "traefik.http.middlewares.customHeader.headers.browserxssfilter=true"
- 
"traefik.http.middlewares.customHeader.headers.referrerPolicy=strict-origin-when-cross-origin"
 
 
- "traefik.http.middlewares.customHeader.headers.stsSeconds=31536000"
- "traefik.http.middlewares.customHeader.headers.stsIncludeSubdomains=true"
- "traefik.http.middlewares.customHeader.headers.stsPreload=true"
- "traefik.http.middlewares.customHeader.headers.forceSTSHeader=true"
- 
"traefik.http.middlewares.customHeader.headers.permissionsPolicy=geolocation=(),midi=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()"
- 
"traefik.http.middlewares.customHeader.headers.customResponseHeaders.Content-Security-Policy-Report-Only=default-src
 
'self' https: data: 'unsafe-inline' 'unsafe-hashes' 'unsafe-eval'; 
object-src 'none';"

## Middlewares HTTP Headers - customRedirectRegex
- 
"traefik.http.middlewares.customRedirectRegex.redirectregex.regex=^https://${DSPACE_REST_HOST:-localhost}/cris/rp/(.*)"
- 
"traefik.http.middlewares.customRedirectRegex.redirectregex.replacement=https://${DSPACE_REST_HOST:-localhost}/lucky-search?index=legacy-id=$${1};

## Middlewares Prevent DDoS attacks - customInflightreq, customRatelimit
- "traefik.http.middlewares.customInflightreq.inflightreq.amount=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.average=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.burst=200"

discovery.xml setting





...








...




Dspace Log
2024-04-12 08:28:20 2024-04-12 08:28:20,462 INFO 
 c5a70b65-bc5f-41ac-83e6-37411c6f4666 964c07c2-de87-4186-b69d-436c9abfc6d2 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/discover/search/objects] originated from 
/entities/person/test1/publications
2024-04-12 08:28:20 2024-04-12 08:28:20,746 ERROR 
c5a70b65-bc5f-41ac-83e6-37411c6f4666 964c07c2-de87-4186-b69d-436c9abfc6d2 
org.dspace.discovery.utils.DiscoverQueryBuilder @ 
ad...@lib.ntu.edu.tw::Error in Discovery while setting up date facet 
range:date facet\colon; 
org.dspace.discovery.configuration.DiscoverySearchFilterFacet@e985418
2024-04-12 08:28:20 org.dspace.discovery.SearchServiceException: Error from 
server at http://dspacesolr:8983/solr/search: 
org.apache.solr.search.SyntaxError: Cannot parse 'author_authority:{0} AND 
search.resourcetype:Item': Encountered " "}" "} "" at line 1, column 19.
2024-04-12 08:28:20 Was expecting:
2024-04-12 08:28:20 "TO" ...
2024-04-12 08:28:20 
2024-04-12 08:28:20 at 
org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:792) 
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.FacetYearRange.calculateNewRangeBasedOnSearchIndex(FacetYearRange.java:113)
 
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.FacetYearRange.calculateRange(FacetYearRange.java:58) 
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.SolrServiceImpl.getFacetYearRange(SolrServiceImpl.java:1692)
 
~[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.utils.DiscoverQueryBuilder.fillFacetIntoQueryArgs(DiscoverQueryBuilder.java:255)
 
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.utils.DiscoverQueryBuilder.addFaceting(DiscoverQueryBuilder.java:442)
 
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.discovery.utils.DiscoverQueryBuilder.buildQuery(DiscoverQueryBuilder.java:125)
 
[dspace-api-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.app.rest.utils.RestDiscoverQueryBuilder.buildQuery(RestDiscoverQueryBuilder.java:96)
 
[dspace-server-webapp-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at 
org.dspace.app.rest.repository.DiscoveryRestRepository.getSearchObjects(DiscoveryRestRepository.java:110)
 
[dspace-server-webapp-cris-2023.02.03.jar:cris-2023.02.03]
2024-04-12 08:28:20 at

[dspace-tech] Error with refresh page

2024-04-11 Thread Jack OE 
Subject: Refresh webpage problem

Hi, we are having a problem with webpage response when trying to refresh a 
page.
On our site when I go through the pages normally by clicking Researchers → 
Publications → Filters (Type: book) the webpage response is fine, the URL 
shows 
"/entities/person/test1/publications?f.itemtype=book,equals=1"

But when I try to refresh the page, I get a 404 error instead.

I tried refresh on the 4Science demo site: 
https://dspacecris7.4science.cloud/entities/person/andreabollini/publications?spc.page=1=Dataset,equals
 
and the webpage response seems to be fine

Not really sure what could be causing the problem, any help is appreciated. 

My Environment
dspaceVersion: "DSpace 7.6.1"
crisVersion: "cris-2023.02.03"

Use Docker
Traefik proxy → Angular → Dspace

Traefik proxy middleware setting
## Middlewares HTTP Headers - customHeader
- 
"traefik.http.middlewares.customHeader.headers.customFrameOptionsValue=SAMEORIGIN"
- "traefik.http.middlewares.customHeader.headers.contentTypeNosniff=true"
- "traefik.http.middlewares.customHeader.headers.browserxssfilter=true"
- 
"traefik.http.middlewares.customHeader.headers.referrerPolicy=strict-origin-when-cross-origin"
 
 
- "traefik.http.middlewares.customHeader.headers.stsSeconds=31536000"
- "traefik.http.middlewares.customHeader.headers.stsIncludeSubdomains=true"
- "traefik.http.middlewares.customHeader.headers.stsPreload=true"
- "traefik.http.middlewares.customHeader.headers.forceSTSHeader=true"
- 
"traefik.http.middlewares.customHeader.headers.permissionsPolicy=geolocation=(),midi=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()"
- 
"traefik.http.middlewares.customHeader.headers.customResponseHeaders.Content-Security-Policy-Report-Only=default-src
 
'self' https: data: 'unsafe-inline' 'unsafe-hashes' 'unsafe-eval'; 
object-src 'none';"

## Middlewares HTTP Headers - customRedirectRegex
- 
"traefik.http.middlewares.customRedirectRegex.redirectregex.regex=^https://${DSPACE_REST_HOST:-localhost}/cris/rp/(.*)"
- 
"traefik.http.middlewares.customRedirectRegex.redirectregex.replacement=https://${DSPACE_REST_HOST:-localhost}/lucky-search?index=legacy-id=$${1};

## Middlewares Prevent DDoS attacks - customInflightreq, customRatelimit
- "traefik.http.middlewares.customInflightreq.inflightreq.amount=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.average=100"
- "traefik.http.middlewares.customRatelimit.ratelimit.burst=200"

Angular Log
2024-04-12 07:54:39 1|dspace-ui  | Environment extended with app config
2024-04-12 07:54:39 1|dspace-ui  | dspace-angular
2024-04-12 07:54:39 1|dspace-ui  | Version: 2023.02.03
2024-04-12 07:54:39 1|dspace-ui  | Environment: Production
2024-04-12 07:54:39 1|dspace-ui  | [HPM] Proxy created: /  -> 
https://cris7test/server/sitemaps
2024-04-12 07:54:39 1|dspace-ui  | [HPM] Proxy created: /  -> 
https://cris7test/server
2024-04-12 07:54:39 1|dspace-ui  | [07:54:39 GMT+0800 (Taipei Standard 
Time)] Listening at http://dspace-angular:4000/
2024-04-12 07:54:46 1|dspace-ui  | 7 rules skipped due to selector errors:
2024-04-12 07:54:46 1|dspace-ui  |   
.custom-file-input:lang(en)~.custom-file-label -> unmatched pseudo-class 
:lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(zh) .ntubox>div -> unmatched 
pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(en) .ntubox>div -> unmatched 
pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(zh) .ntubox>div:nth-child(2) 
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(en) .ntubox>div:nth-child(2) 
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(zh) .ntubox>div:nth-child(3) 
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  |   html:lang(en) .ntubox>div:nth-child(3) 
-> unmatched pseudo-class :lang
2024-04-12 07:54:46 1|dspace-ui  | GET 
/entities/person/test1?f.itemtype=report,equals=1 404 3140.960 ms 
- -

Dspace Log
2024-04-12 08:09:23 2024-04-12 08:09:23,360 INFO  unknown 
09ee14dd-3697-4b40-8dfb-31580ccbb412 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,390 INFO 
 c5a70b65-bc5f-41ac-83e6-37411c6f4666 78aedb62-49d0-4e84-bf0a-9d53f0f44b3a 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/authn/status] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,406 INFO 
 c5a70b65-bc5f-41ac-83e6-37411c6f4666 a0d50ad1-967f-43b9-aaa1-a182465c9f85 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/config/properties/user-agreement.enabled] originated from /
2024-04-12 08:09:23 2024-04-12 08:09:23,584 INFO 
 c5a70b65-bc5f-41ac-83e6-37411c6f4666 4f1b604b-1a11-4c44-a2f4-86782a951508 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/layout/sections/search/visibleTopBarSections] originated 
from /
2024-04-12

[dspace-tech] Pull community name and collection name from postgres DB

2024-04-11 Thread Kim, Joshua 
Hello,

We have a long list of items which need to show a hierarchy (under which 
community name and collection name). How can I pull the data by using  Postgres 
DB? I am looking at the DB schema, but I am confused. Or the other way? Can 
anyone help me out with this?




[University of Delaware]

Joshua Kim

Library, Museums and Press
josh...@udel.edu

-- 
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/MW4PR10MB629851504DC1C71310242CA7C9052%40MW4PR10MB6298.namprd10.prod.outlook.com.

[dspace-tech] Re: SOLR vulnerabilities in v6 (and v5!)?

2024-04-11 Thread Edmund Balnaves 
As long as you are not exposing the DSpace SOLR to the public web 
interface, the scope of this issue is limited.   You should however at 
least take the upgrade to DSpace 6.4.

Edmund



On Thursday, April 11, 2024 at 9:52:16 PM UTC+10 Michael White wrote:

> Hi,
>
>  
>
> We have 2 DSpace repositories – our main IR, which is DSpace v6.2, and a 
> Data repository, which is DSpace v5.2 (yes, I know, both well out of 
> support and neither is the latest version on their respective branches!) – 
> both using the JSP UI – both are (very) heavily customised, which makes 
> upgrades hard (so can’t just pop on the latest v6 or v5 releases) . . . 
>
>  
>
> A colleague from our infrastructure team has contacted me as their 
> vulnerability scanning software has identified issues with SOLR (on both 
> systems), and he has asked me if it possible to upgrade SOLR on those 
> servers to (hopefully!) eradicate the identified vulnerabilities.
>
>  
>
> This is the list he sent me:
>
>  
>
> Apache Solr: CVE-2017-3164: SSRF issue in Apache Solr
>
> Apache Solr: CVE-2019-0193: Apache Solr, Remote Code Execution via 
> DataImportHandler
>
> Apache Solr: CVE-2019-12401: XML Bomb in Apache Solr versions prior to 5.0
>
> Apache Solr: CVE-2020-13941: Apache Solr information disclosure 
> vulnerability
>
> Apache Solr: CVE-2021-27905: SSRF vulnerability with the Replication 
> handler
>
> Apache Solr: CVE-2021-29262: Misapplied Zookeeper ACLs can result in 
> leakage of configured authentication and authorization settings
>
> Apache Solr: CVE-2021-29943: Apache Solr Unprivileged users may be able to 
> perform unauthorized read/write to collections
>
>  
>
> Does anyone know if DSpace v6.2 and/or v5.2 are vulnerable to any of 
> these, or know where I can look to find out – I tried searching the DSpace 
> documentation/release notes/mailing list but didn’t find any mention of any 
> of these, but I could just not be looking in the right place! (or maybe 
> that means DSpace is not vulnerable?) . . . 
>
>  
>
> And, if any of these vulnerabilities are exploitable in either version 
> v6.2 or v5.2, does anyone know any way to resolve the issues in a “light 
> touch” way (i.e. without doing a full upgrade) – e.g. “just” change the 
> version number(s) in the (SOLR) POM, or apply this or that patch/diff (to 
> update bits of DSpace that are affected) . . . ?
>
>  
>
> Of course, the upgrade to v7 (or even v8!) is still on my to do list, but 
> it’s still a way down the road due to other priorities, so I need to 
> patch/fudge my way round this for the time being (assuming any of these are 
> an issue of course!) . . . 
>
>  
>
> Any information, pointers, or suggestions that anyone may have would be 
> very welcome.
>
>  
>
> Cheers,
>
>  
>
> Mike
>
>  
>
>
>
> *Michael White Senior Developer Product Development*
>
>
> *Information Services *University of Stirling
> Stirling
> FK9 4LA
>
> Tel: +44 (0) 1786 466877 <+44%201786%20466877>
> Email: michael.wh...@stir.ac.uk
> Web: Information Services 
> 
>
>  
>
> My normal working hours are: Mon-Fri, 8.30-4.30
>
> [image: Facebook icon]  [image: 
> X icon]  [image: Instagram icon] 
>  [image: Youtbue icon] 
> 
>
> [image: Banner] 
>
>  
>
>  
> --
> Scotland’s University for Sporting Excellence
> The University of Stirling is a charity registered in Scotland, number SC 
> 011159
>

-- 
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/e3ef57aa-13e4-4c36-8c5a-9b1075aef40en%40googlegroups.com.

[dspace-tech] SOLR vulnerabilities in v6 (and v5!)?

2024-04-11 Thread Michael White 
Hi,

We have 2 DSpace repositories – our main IR, which is DSpace v6.2, and a Data 
repository, which is DSpace v5.2 (yes, I know, both well out of support and 
neither is the latest version on their respective branches!) – both using the 
JSP UI – both are (very) heavily customised, which makes upgrades hard (so 
can’t just pop on the latest v6 or v5 releases) . . .

A colleague from our infrastructure team has contacted me as their 
vulnerability scanning software has identified issues with SOLR (on both 
systems), and he has asked me if it possible to upgrade SOLR on those servers 
to (hopefully!) eradicate the identified vulnerabilities.

This is the list he sent me:

Apache Solr: CVE-2017-3164: SSRF issue in Apache Solr
Apache Solr: CVE-2019-0193: Apache Solr, Remote Code Execution via 
DataImportHandler
Apache Solr: CVE-2019-12401: XML Bomb in Apache Solr versions prior to 5.0
Apache Solr: CVE-2020-13941: Apache Solr information disclosure vulnerability
Apache Solr: CVE-2021-27905: SSRF vulnerability with the Replication handler
Apache Solr: CVE-2021-29262: Misapplied Zookeeper ACLs can result in leakage of 
configured authentication and authorization settings
Apache Solr: CVE-2021-29943: Apache Solr Unprivileged users may be able to 
perform unauthorized read/write to collections

Does anyone know if DSpace v6.2 and/or v5.2 are vulnerable to any of these, or 
know where I can look to find out – I tried searching the DSpace 
documentation/release notes/mailing list but didn’t find any mention of any of 
these, but I could just not be looking in the right place! (or maybe that means 
DSpace is not vulnerable?) . . .

And, if any of these vulnerabilities are exploitable in either version v6.2 or 
v5.2, does anyone know any way to resolve the issues in a “light touch” way 
(i.e. without doing a full upgrade) – e.g. “just” change the version number(s) 
in the (SOLR) POM, or apply this or that patch/diff (to update bits of DSpace 
that are affected) . . . ?

Of course, the upgrade to v7 (or even v8!) is still on my to do list, but it’s 
still a way down the road due to other priorities, so I need to patch/fudge my 
way round this for the time being (assuming any of these are an issue of 
course!) . . .

Any information, pointers, or suggestions that anyone may have would be very 
welcome.

Cheers,

Mike

Michael White
Senior Developer
Product Development
Information Services
University of Stirling
Stirling
FK9 4LA

Tel: +44 (0) 1786 466877
Email: michael.wh...@stir.ac.uk
Web: Information 
Services

My normal working hours are: Mon-Fri, 8.30-4.30
[Facebook icon] [X icon] 
  [Instagram icon] 
  [Youtbue icon] 

[Banner]

[cid:image006.png@01DA8C0C.4A199E20]


Scotland’s University for Sporting Excellence
The University of Stirling is a charity registered in Scotland, number SC 011159

-- 
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/DBBPR03MB703513D52D9296DEFD5BCE15D4052%40DBBPR03MB7035.eurprd03.prod.outlook.com.

Re: [dspace-tech] Mode of upgrading a DSpace repository from version 6 to 7 or 8

2024-04-11 Thread 'gustav chinovava' via DSpace Technical Support 
 The access URL to a DSpace 7 repository is a combination of configurations 
below.(1)Your local/public DNS (2)Apache2 config or whatever web server 
used(3)DSpace local.cfg and angular ui config files(4)In my case server hosts 
file
The URL is detached from the database in my view.
On Thursday, April 11, 2024 at 11:39:46 AM GMT+2, admin 
 wrote:  
 
 Hello Gustav,
Thanks. And can I test DSpace under temporary url and the move it into final 
destination just by changing url in DSpace config? Or the url is also included 
in the database so moving DSpace to a new url wouldn't be that easy?
Peter

środa, 10 kwietnia 2024 o 13:40:27 UTC+1 gustav chinovava napisał(a):

 Hi Peter 

As far as I know, handles reside in the postgreSQL database (table 'handle').
So a dump of you dspace database in 6.x, followed by a restore on the 
newly-installed 7.x should do the trick.But of course do perform tests.
And the 6.x restored database need a migrate task on it so one gets the 7.x 
schema.
Regards
On Wednesday, April 10, 2024 at 02:28:45 PM GMT+2, admin 
 wrote:  
 
 Hello,
I am now considering various approaches to upgrade DSpace from ver. 6 to 7 or 8.
Would it be feasible to install a fresh new DSpace version and then import 
publications from the old repository, but preserving specific elements like 
item handles? Or traditional way of upgrading would be eventually less 
challenging? I don't care about any UI customization, but obviously keeping the 
current handles would be critical.
ThanksPeter

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/bd557ebc-0b7d-4ac9-900a-a607fbd7899bn%40googlegroups.com.
  


-- 
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/9184734e-db94-4b76-9a3b-eeca6906db14n%40googlegroups.com.
  

-- 
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/1117212274.8688022.1712830776272%40mail.yahoo.com.

Re: [dspace-tech] Mode of upgrading a DSpace repository from version 6 to 7 or 8

2024-04-11 Thread admin 
Hello Gustav,

Thanks. And can I test DSpace under temporary url and the move it into 
final destination just by changing url in DSpace config? Or the url is also 
included in the database so moving DSpace to a new url wouldn't be that 
easy?

Peter

środa, 10 kwietnia 2024 o 13:40:27 UTC+1 gustav chinovava napisał(a):

> Hi Peter 
>
> As far as I know, handles reside in the postgreSQL database (table 
> 'handle').
>
> So a dump of you dspace database in 6.x, followed by a restore on the 
> newly-installed 7.x should do the trick.
> But of course do perform tests.
>
> And the 6.x restored database need a migrate task on it so one gets the 
> 7.x schema.
>
> Regards
>
> On Wednesday, April 10, 2024 at 02:28:45 PM GMT+2, admin <
> ad...@ispan.edu.pl> wrote: 
>
>
> Hello,
>
> I am now considering various approaches to upgrade DSpace from ver. 6 to 7 
> or 8.
>
> Would it be feasible to install a fresh new DSpace version and then import 
> publications from the old repository, but preserving specific elements like 
> item handles? Or traditional way of upgrading would be eventually less 
> challenging? I don't care about any UI customization, but obviously keeping 
> the current handles would be critical.
>
> Thanks
> Peter
>
> -- 
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/bd557ebc-0b7d-4ac9-900a-a607fbd7899bn%40googlegroups.com
>  
> 
> .
>

-- 
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/9184734e-db94-4b76-9a3b-eeca6906db14n%40googlegroups.com.