Hi Michael
I think this depends on how you set the following parameter in the local or
dspace cfg.If such uri's are meant to be persistent (and used for citations), I
would avoid a value that includes my domain - since domain is bound to change -
and leave it pointing to the handle base URL.
Hi,
Am 12.04.24 um 11:25 schrieb admin:
Okay, so apparently moving the site to a new url without manipulating
database could be painless.
[…]
I'd say: partial.
Your metadata will presumably contain the full URL in "identifier.url"
(select * from metadatavalue where metadata_field_id =34;) ,
Okay, so apparently moving the site to a new url without manipulating
database could be painless.
Thank you, will be testing it further.
czwartek, 11 kwietnia 2024 o 11:19:45 UTC+1 gustav chinovava napisał(a):
> The access URL to a DSpace 7 repository is a combination of configurations
>
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
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
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
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
