Hi all!
I'm seeing an odd behaviour on my Dspace 6.3. Whenever there is a new item
submission, the dc.date.accessioned and dc.date.available are saved with
UTC time but it should be with the local time that my server and database
have:
[image: imagen_2022-02-08_083220.png]
Do you guys know if
Upgrading DSpace 7.x (7.1 to 7.2), upgrading the Front-end, step 'C' says I
should use yarn to convert the earlier installation's .ts files to .yml. I
am not able to get past this step. Perhaps I only need some assistance in
the specific grammar in using the conversion script.
The path to my
On Mon, Feb 07, 2022 at 07:32:01AM -0800, Mohammad S. AlMutairi wrote:
> On Monday, February 7, 2022 at 4:14:26 PM UTC+3 Mark H. Wood wrote:
>
> > The three processes (dspace-server-webapp, dspace-angular, solr)
> > interact only through network connections. They do not need direct
> > access to
Hi Chris,
That "yarn env:yaml" command only requires one input, whish is your old
"environment.*.ts" file. So, that second input is *optional*. If you only
give it one input, it'll write the output YAML file into that same
directory. That's perfectly ok...you'd just want to eventually ensure
Hi,
Unfortunately, we'd need more information about your setup. That error
message is just saying that either your email address or password was
incorrect. So, you may want to double check that your email is really
"myemail" (which appears to be what you entered), and make sure you typed
the
Dear colleagues,
I'm having problems using api-rest from dspace 6.3 for blocked cors-origin.
How can I get around this situation?
Thanks in advance.
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You rece
Hi Juan,
At the database level, DSpace will only save dates in UTC format (this is
true for any version of DSpace, including 7.x). So, all dates are
formatted to UTC before they are saved in the database as metadata. This is
necessary to make things like time-base access restrictions (e.g.
em
Thanks, Tim, but still frustrated!
I understand you are saying to go to my old /src/environments directory,
and run this command:
yarn env:yaml environment.prod.ts
Here is the response I get:
root@melo4:/opt/dspace-angular-old/src/environments# yarn env:yaml
environment.prod.ts
yarn run v1.22.17
Configuration question I guess.
I am a member of the Administrators group. However when I log in, most of
the administrator actions on the sidebar are not available to me (for
instance, create a community/collection, access control, administer
workflow etc). The only options available are create
Hi Bill,
Those side menus should be checking which groups you are a member of
automatically (by querying the backend/REST API when you login). They are coded
to do so in the AdminSidebar component, starting around here:
https://github.com/DSpace/dspace-angular/blob/main/src/app/admin/admin-side
Hi Chris,
It sounds like our the docs need clarifying here. You need to run `yarn
env:yaml` from the *NEW 7.2 codebase directory*. Since you are trying to
run it from your old 7.1 code, it is throwing an error as that command
didn't exist in the 7.1 codebase.
So, the docs were written assumi
Sorry, forgot to copy the list.
In the apache logs, I see a number of GETs that look like:
/server/api/authz/authorizations/search/object?uri=
https://udc-prd.lib.umn.edu/server/api/core/sites/0175ee52-5642-4302-89a1-99c444e5bd2c&feature=isCollectionAdmin&embed=feature
Is this what you are refer
Still doesn't work and I think I know why. The environment.prod.ts file
declares 4 files to import, so the script is unable to find them if
environment.prod.ts is placed in some arbitrary location under the DSpace
7.2 angular root directory. Shall I presume that these import paths need
to poi
Hi Bill,
Yes, those GET requests are your UI attempting to check your permissions on the
backend.
The one you sent has a "uri" equal to your "Site object", and a
"feature=isCollectionAdmin". That means it's attempting to check if you have
Collection Admin rights on any Collection in the enti
Ouch!
These 4 imports in environment.prod.ts, in turn refer to all sorts of other
.ts files from the old installation. It is not as simple as copying four
files over, in addition to environment.prod.ts and place under the DSpace
7.2 angular code root.
Okay - From the DSpace 7.2 angular root di
Ouch!
These 4 imports in environment.prod.ts, in turn refer to all sorts of other
.ts files from the old installation. It is not as simple as copying four
files over, in addition to environment.prod.ts and place under the DSpace
7.2 angular code root.
Okay - From the DSpace 7.2 angular root di
Hi Chris,
You are 100% correct. It looks like during 7.2 development, after we
created the "yarn env:yaml" script, we then moved some code around, and
broke those imports at the top of the old "environment.prod.ts". So, if
you copy it over into the 7.2 directory structure, it won't work beca
Thank you. Yes, it is a bit awkward.
I kept and renamed my 7.1 angular directory and properly referenced
"environment.prod.ts" in the yarn command. I moved the new config.prod.yml
to it's proper place and ran the " yarn run build:prod" command to build
the final production version.
I will late
So, I tried creating a new admin with an even easier password. now it
works. Maybe there is some issue with the first few created admins. I
located the eperson table in pgadmin 3, it shows that all of the admin
emails are correct but i dont know about the password. Thanks for your
time, Sir!
O
On Tuesday, February 8, 2022 at 7:23:55 PM UTC+3 Mark H. Wood wrote:
> Well, Ubuntu Focal has Solr in its package repository, but it's a
> decade old, so Ubuntu is one of the distro.s on which you need to do
> the installation manually. That means you'll need to create a user to
> run it, very
On Wednesday, February 9, 2022 at 2:47:08 AM UTC+3 Chris Clawson wrote:
> Everything seemed to finish well, although a full system reboot failed to
> start angular as a service. I guess this is my last barrier to a
> functional upgrade, but it is the stuff of a new thread if I need help.
>
You
21 matches
Mail list logo
