[dspace-tech] Re: help - our repository administrator account was accidentally deleted

[Romy Forrer]

Thanks Stuart - we do have other administrator accounts already so can 
still do admin things ok (the one that got deleted was the original one 
created via that script many moons ago). 
Before posting this I didn't realise there was functionality in Dspace 7 to 
allow for deletion of e-person accounts with associated submissions (since 
found the PR related to it), was actually wondering how on earth it 
happened in the first place.  
Now we are grappling with whether to try and reinstate that account and all 
its ties to former submissions via database edits (seems like it will be a 
bit painful to update all the right tables) or just to let it go, leave the 
submissions as orphans and create a new admin account with the same groups 
as the old one to use going forward.  Unsure if there are now some items 
possibly stuck in workflow pools or if the account deletion process would 
have taken care of all that nicely - if the latter is true we will likely 
not bother to try and reconnect the orphan submissions.  

Kind Regards,

Romy

On Friday, September 22, 2023 at 3:36:16 PM UTC+12 sye...@gmail.com wrote:

> Assuming that you're running 6.x or 7.x, there's a command documented at 
> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace for creating a 
> new dspace administrator account.
>
> cheers
> stuart
>
> On Friday, 22 September 2023 at 10:02:26 UTC+12 Romy Forrer wrote:
>
>> Hi there
>>
>> Hoping someone can advise on the best course of action to deal with 
>> someone accidentally deleting our administrator eperson account.  
>> Luckily we have another one with admin privileges as well so can still 
>> perform admin functions but I am worried that deleting the original one 
>> will have functional consequences.
>>  
>> We are on Dspace 7.6 and migrated/copied over our dspace 6.3 PostGres 
>> database plus have a dev/test server where the account still exists so I 
>> have the eperson data, plus epersongroup2eperson data that is likely to 
>> still be current from the database.
>> However there will have been other tables with associations to that 
>> eperson_id to try and re-populate.  Is there a list somewhere of all the 
>> tables where that eperson would typically be referenced?
>> Is it relatively safe to insert an eperson to the database via SQL (We 
>> have a DBeaver interface we use to query the database etc.) or should we be 
>> creating the account fresh via the admin GUI?  
>> We do keep postgres database backups but I have never had to load any 
>> before and am not all that confident to reload from backup (alas our most 
>> experienced dspace colleague is away on holiday) and don't want to risk 
>> losing new submission added since last backup.
>>
>> Be fantastic to get some advice around how to handle this.
>>
>> Kind Regards,
>>
>> Romy 
>>
>> Romy Forrer
>> Library Systems Coordinator
>> University of Canterbury
>>  
>>
>

-- 
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/3be9e3de-593f-4b54-ab09-87e8f4df88e9n%40googlegroups.com.

[dspace-tech] Re: help - our repository administrator account was accidentally deleted

[sye...@gmail.com]

Assuming that you're running 6.x or 7.x, there's a command documented 
at https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace for creating 
a new dspace administrator account.

cheers
stuart

On Friday, 22 September 2023 at 10:02:26 UTC+12 Romy Forrer wrote:

> Hi there
>
> Hoping someone can advise on the best course of action to deal with 
> someone accidentally deleting our administrator eperson account.  
> Luckily we have another one with admin privileges as well so can still 
> perform admin functions but I am worried that deleting the original one 
> will have functional consequences.
>  
> We are on Dspace 7.6 and migrated/copied over our dspace 6.3 PostGres 
> database plus have a dev/test server where the account still exists so I 
> have the eperson data, plus epersongroup2eperson data that is likely to 
> still be current from the database.
> However there will have been other tables with associations to that 
> eperson_id to try and re-populate.  Is there a list somewhere of all the 
> tables where that eperson would typically be referenced?
> Is it relatively safe to insert an eperson to the database via SQL (We 
> have a DBeaver interface we use to query the database etc.) or should we be 
> creating the account fresh via the admin GUI?  
> We do keep postgres database backups but I have never had to load any 
> before and am not all that confident to reload from backup (alas our most 
> experienced dspace colleague is away on holiday) and don't want to risk 
> losing new submission added since last backup.
>
> Be fantastic to get some advice around how to handle this.
>
> Kind Regards,
>
> Romy 
>
> Romy Forrer
> Library Systems Coordinator
> University of Canterbury
>  
>

-- 
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/0dd28b3a-dbd0-46d5-bb1a-b8b27000dd2fn%40googlegroups.com.

[dspace-tech] help - our repository administrator account was accidentally deleted

[Romy Forrer]

Hi there

Hoping someone can advise on the best course of action to deal with someone 
accidentally deleting our administrator eperson account.  
Luckily we have another one with admin privileges as well so can still 
perform admin functions but I am worried that deleting the original one 
will have functional consequences.
 
We are on Dspace 7.6 and migrated/copied over our dspace 6.3 PostGres 
database plus have a dev/test server where the account still exists so I 
have the eperson data, plus epersongroup2eperson data that is likely to 
still be current from the database.
However there will have been other tables with associations to that 
eperson_id to try and re-populate.  Is there a list somewhere of all the 
tables where that eperson would typically be referenced?
Is it relatively safe to insert an eperson to the database via SQL (We have 
a DBeaver interface we use to query the database etc.) or should we be 
creating the account fresh via the admin GUI?  
We do keep postgres database backups but I have never had to load any 
before and am not all that confident to reload from backup (alas our most 
experienced dspace colleague is away on holiday) and don't want to risk 
losing new submission added since last backup.

Be fantastic to get some advice around how to handle this.

Kind Regards,

Romy 

Romy Forrer
Library Systems Coordinator
University of Canterbury
 

-- 
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/34fb4710-adc8-42f5-9125-fef3de0d82b0n%40googlegroups.com.

Re: [dspace-tech] Unable to use IIIF in Private Community/Collection

[Chris Clawson]

Thank you! I am very sad to hear that by grateful for the answer, which 
prevents me from wasting more time on the problem. Please post a public 
procedure at such time that one might support the DSpace core release.
Chris

On Thursday, September 21, 2023 at 2:48:24 AM UTC-4 Bollini, Andrea wrote:

> Using IIIF over restricted content is not currently supported out-of-box 
> by DSpace. It requires some customization and careful configuration of the 
> infrastructure.
> We, at 4Science, are currently able to manage that with our commercial 
> extension.
> With the community we are working for a long term solution in the official 
> DSpace see https://github.com/DSpace/dspace-angular/issues/1435
>
> Andrea
>
>
> -- 
> Andrea Bollini
> Chief Technology and Innovation Officer
>
> 4Science, www.4science.com, ISO 9001:2015, CSA Trusted Cloud Provider
> Certified Platinum Provider of DSpace, DSpace-CRIS, DSpace-GLAM
>
> 4Science USA - 435 Nichols Road Suite 200, Kansas City, MO 64112
> 4Science Europe - Viale Achille Papa 30, World Join Center Tower, 20149 
> Milano, Italy
> mobile: +39 333 934 1808 <+393339341808>
> linkedin: andreabollini
> orcid: -0002-9029-1854
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of DSpace Technical Support 
> *Sent:* Monday, September 18, 2023 8:36 PM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Unable to use IIIF in Private 
> Community/Collection 
>  
> I am trying to provide Mirador and IIIF image viewing in a Community and 
> Collection restricted from public view.
> I have a special user group defined and have set default read, write and 
> submit privileges to that group.
> EPerson members of that group will see the community once they have logged 
> in. I have one Collection defined and the one Item within that Collection 
> has dspace.iiif.enabled set to 'true'.
> When I view the item, the Mirador viewer draws but there is nothing inside 
> the viewer. No error is reported and no metadata is displayed.
> All of my public Communities and Items (with IIIF enabled) display 
> normally. It is only this restricted community which won't display IIIF 
> content.
> Might somebody help me solve this problem, please? I am happy to provide 
> more detail.
>
> -- 
> 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/4a3a19ed-0737-41f5-8e3a-ddaf029d7084n%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/d27871a5-e1d7-4329-afca-60268e919e0dn%40googlegroups.com.

[dspace-tech] Error 403 | front end (login) | "POST http:///server/api/authn/login 403"

[Michel Montenegro]

Frontend Information (error):

   - Error: *403 *
   - Local: *Try Login*
   - Return error: "*POST http:///server/api/authn/login 403*"


Geral Information:

   - TomCat
  - uses port 80.
   - Frontend
  - Uses port 80 and ssl(false)
   - Backend
  - dspace.server.url = http://172.17.0.10*:80*/server


What could be generating this error?

-- 
Atenciosamente,
*Michel Pinheiro Montenegro*
- *Bacharel* em Sistema de Informação
- [Lato Sensu] *Especialista* em Engenharia de Sistemas
- [Stricto Sensu] *Mestre* em Ciência da Computação
- [Stricto Sensu] *Doutorando* em Ciência da Computação

E-mail/Gtalk: michel.montene...@gmail.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/CADOAx_j0nZm6yDRLd9Dk%2BK28GxiPYB%3DB3NhjGqvw7N6HVavZ2g%40mail.gmail.com.

Re: [dspace-tech] Embargo date can't be more than 3 years in the future?

[Paige Morgan]

Thanks, Sean! That does indeed seem to be what I needed.

Paige

-
*Meeting/regular work hours: Monday - Friday, 9am-4:30pm*

Dr. Paige C. Morgan
(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape land
)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
available via Zoom, phone, etc.)
*** I observe email-free evenings and weekends. ***


On Wed, Sep 20, 2023 at 12:32 PM Sean Kalynuk 
wrote:

> Hi Paige,
>
>
>
> The relevant documentation you are looking for can be found here:
>
>
>
>
> https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams
>
>
>
> --
>
> Sean
>
>
>
> *From: *dspace-tech@googlegroups.com  on
> behalf of Paige Morgan 
> *Date: *Wednesday, September 20, 2023 at 11:03 AM
> *To: *DSpace Technical Support 
> *Subject: *[dspace-tech] Embargo date can't be more than 3 years in the
> future?
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
>
> Hi, all--
>
>
>
> We're running DSpace 7.4, and we recently ran into an issue when trying to
> set an embargo for an open-access version of a scholarly publication. The
> publication has a 48-month embargo, but the interface won't let us set an
> embargo date that is later than September 2026 (36 months).
>
>
>
> I thought this might be a local setting for us, but I found the same limit
> in the demo.dspace.org sandbox -- though I'm not finding any indication
> in the documentation 
> that the 36-month limit is intentional. Is this a hard limit, or just a
> configuration setting that we need to change?
>
>
>
> Thanks in advance!
>
> Paige
>
>
>
> -
>
> *Meeting/regular work hours: Monday - Friday, 9am-4:30pm*
>
>
>
> *Dr. Paige C. Morgan*
>
> (she/they)
> Digital Publishing and Copyright Librarian,
> Head of Digital Initiatives & Preservation
> University of Delaware Library, Museums and Press (on Lenape land
> )
> Morris 118
> ORCID: https://orcid.org/-0001-8076-7356
> paig...@udel.edu
> 302.831.7153
>
> Make an appointment to meet with me: https://calendly.com/paigecm/ (Meetings
> available via Zoom, phone, etc.)
> *** I observe email-free evenings and weekends. ***
>
>
>
> --
> 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/CA%2BzEVdkE-JXOacdoJh-JnkFjgneOq00MfYgEb%2BxvLsrojLG6fw%40mail.gmail.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/CA%2BzEVd%3DoAz9Ab5c0w9EmdrhwTTigZE%2BDa4__WU1uTJa2osG_Zw%40mail.gmail.com.

[dspace-tech] dspace 7 SSL Problem

[Vivek Kumar]

I have installed DSpace 7.6 on Debian 12. On the local server all things
are working fine over HTTP with my local IP address.  Now this address is
bind with a sub-domain in the DNS server where the auto redirect rule is
set to forward all HTTP requests to HTTPS. And SSL server is also setup at
domain server only. The DNS server is not handled by our library and SSL
server refused to forward HTTP requests directly.

So, we can access the DSpace url via HTTPS only. But as local setup is HTTP
only, DSpace denies many requests like PDF file not opened, login not
working. Can anybody suggest a possible solution which can work in my
scenario. I shall be thankful to you.



Thanking you,
Vinod Kumar

-- 
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/CAJWbGf88XSEYLSMCdN340AKTqiREhmg%2BitaANs96J%3DSgLCP9hg%40mail.gmail.com.

Re: [dspace-tech] Unable to use IIIF in Private Community/Collection

['Bollini, Andrea' via DSpace Technical Support]

Using IIIF over restricted content is not currently supported out-of-box by 
DSpace. It requires some customization and careful configuration of the 
infrastructure.
We, at 4Science, are currently able to manage that with our commercial 
extension.
With the community we are working for a long term solution in the official 
DSpace see https://github.com/DSpace/dspace-angular/issues/1435

Andrea


--
Andrea Bollini
Chief Technology and Innovation Officer

4Science, www.4science.com, ISO 9001:2015, CSA 
Trusted Cloud Provider
Certified Platinum Provider of DSpace, DSpace-CRIS, DSpace-GLAM

4Science USA - 435 Nichols Road Suite 200, Kansas City, MO 64112
4Science Europe - Viale Achille Papa 30, World Join Center Tower, 20149 Milano, 
Italy
mobile: +39 333 934 1808
linkedin: andreabollini
orcid: -0002-9029-1854

From: dspace-tech@googlegroups.com  on behalf of 
DSpace Technical Support 
Sent: Monday, September 18, 2023 8:36 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Unable to use IIIF in Private Community/Collection

I am trying to provide Mirador and IIIF image viewing in a Community and 
Collection restricted from public view.
I have a special user group defined and have set default read, write and submit 
privileges to that group.
EPerson members of that group will see the community once they have logged in. 
I have one Collection defined and the one Item within that Collection has 
dspace.iiif.enabled set to 'true'.
When I view the item, the Mirador viewer draws but there is nothing inside the 
viewer. No error is reported and no metadata is displayed.
All of my public Communities and Items (with IIIF enabled) display normally. It 
is only this restricted community which won't display IIIF content.
Might somebody help me solve this problem, please? I am happy to provide more 
detail.

--
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/4a3a19ed-0737-41f5-8e3a-ddaf029d7084n%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/DB9P189MB17074A38DE1C4CFBD6028376A5F8A%40DB9P189MB1707.EURP189.PROD.OUTLOOK.COM.

Re: [dspace-tech] Implementing Clicky statistics From Angulartics2 in DSpace-CRIS 2022.03.00 (DSpace 7.4)

['Bollini, Andrea' via DSpace Technical Support]

Hi Muhamd,
it is not a trivial task, it would be not sufficient to inject the html snippet 
that they provide as easier integration path.
To have an idea about which are of the angular and rest application are 
impacted you can take a look to the PR where we have integrated google 
analytics (please check also the corresponding REST PR)
https://github.com/DSpace/dspace-angular/pull/1826

Hope this help,
Andrea


--
Andrea Bollini
Chief Technology and Innovation Officer

4Science, www.4science.com, ISO 9001:2015, CSA 
Trusted Cloud Provider
Certified Platinum Provider of DSpace, DSpace-CRIS, DSpace-GLAM

4Science USA - 435 Nichols Road Suite 200, Kansas City, MO 64112
4Science Europe - Viale Achille Papa 30, World Join Center Tower, 20149 Milano, 
Italy
mobile: +39 333 934 1808
linkedin: andreabollini
orcid: -0002-9029-1854

From: dspace-tech@googlegroups.com  on behalf of 
Muhamad Aiman Zikri 
Sent: Wednesday, September 20, 2023 3:30 AM
To: DSpace Technical Support 
Subject: [dspace-tech] Implementing Clicky statistics From Angulartics2 in 
DSpace-CRIS 2022.03.00 (DSpace 7.4)

Hi!

My institution has request for implementing Clicky statistics 
(https://clicky.com/) into our repository which is based on DSpace-CRIS 
2022.03.00 (DSpace 7.4). I have tried to understand on how to implement the 
code of this provider in angular generally but it seems too different and 
complicated when comes to DSpace configuration.

So, if anyone has any idea on which part of DSpace files that I need to 
implement the code to make it work. And if possible, kindly provides 
step-to-step guide to implement new statistics provider in DSpace as I'm still 
new in DSpace and Angular.

Thank you.

--
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/b743341b-24d3-4a92-ba16-cf6bff889147n%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/DB9P189MB170781CE0EE61441769BABE9A5F8A%40DB9P189MB1707.EURP189.PROD.OUTLOOK.COM.