[dspace-tech] Re: Remove restrictions on entire collection with items

[Lewatle Johannes Phaladi]

Hi DSpace Team,

How can I open the whole collection for anonymous or non logged in users.

Regards,
Lewatle 

On Tuesday, 23 October 2018 15:32:15 UTC+2, Lewatle Johannes Phaladi wrote:
>
> Dear DSpace Team,
>
> I have collection with more than 300 items which are closed for anonymous 
> access, I cant go manually one by one changing individual items 
> authorization policy to allow anonymous user access. Please share with me 
> how to remove restrictions on collection for public / anonymous access.
>
> Regards,
> Lewatle 
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Remove restrictions on entire collection with items

[Claudia Jürgen]

Hello,

for future items set the
DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ to anonymous
for existing items, which have been submitted with restriction
log in as admin -> Administer -> Access Control -> Authorization ->
Advanced/Item Wildcard Policy Admin Tool
there you can change the existing items

Hope this helps

Claudia Jürgen


Am 24.10.2018 um 09:14 schrieb Lewatle Johannes Phaladi:

Hi DSpace Team,

How can I open the whole collection for anonymous or non logged in users.

Regards,
Lewatle

On Tuesday, 23 October 2018 15:32:15 UTC+2, Lewatle Johannes Phaladi wrote:

Dear DSpace Team,

I have collection with more than 300 items which are closed for anonymous
access, I cant go manually one by one changing individual items
authorization policy to allow anonymous user access. Please share with me
how to remove restrictions on collection for public / anonymous access.

Regards,
Lewatle



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Authorization policy of collection not opening for previously submitted items on DSpace 6.2

[Lewatle Johannes Phaladi]

Dear DSpace Team,

I have edited authorization policy directly on collection and added Read, 
Default_Bitstream_Read and Default_Item Read for Anonymous user, I have 
then tried to open older submitted items and they are still restricted for 
non-logged in users, i have done test submission to check if new items are 
accessible to anonymous users and yes they are accessible, I would like to 
know if there is way to open previously submitted items under collection 
without changing policy on item one by one.

Regards,
Lewatle 

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: DOI via Proxy

[Paul Münch]

Hello again,

after database manipulating the original proxy problem persists.
Fortunately I found a solution.

The 'HttpClientBuilder' (
https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-api/src/main/java/org/dspace/identifier/doi/DataCiteConnector.java#L769
) do not use proxy settings. So I add some code:

HttpHost proxy = new HttpHost(configurationService.getProperty(CFG_PROXY_HOST), 
Integer.parseInt(configurationService.getProperty(CFG_PROXY_PORT)), "http"); 
httpclient = HttpClientBuilder
.create()
.setDefaultCredentialsProvider(credentialsProvider)
.setRetryHandler(new StandardHttpRequestRetryHandler(3, true))
.setProxy(proxy)
.build();

Now everything works fine.

Kind regards,

Paul Münch

Am 23.10.18 um 09:44 schrieb Paul Münch:
> As an addition to Claudia's database command. We have a DSpace 6.3
> instance and so the command is a little bit different:
> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status, 
> dspace_object) 
> SELECT nextval('doi_seq'), 
> concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 
> 7, dspace_object
> FROM item WHERE in_archive=true and uuid not in (select uuid from doi where 
> resource_type_id=2);
> Am 22.10.18 um 13:35 schrieb Claudia Jürgen:
>> Hello Paul,
>>
>> once you have configured and your DOI ( these notes are for4.x, 5.x) in
>> [dspace]/dspace/config/dspace.cfg
>>
>>   * identifier.doi.prefix
>>   * identifier.doi.namespaceseparator
>>   * event.consumer.doi.class
>>   * event.consumer.doi.filters
>>   * event.dispatcher.default.consumers
>>
>> [dspace]/config/spring/api/identifier-service.xml
>>
>>   * bean org.dspace.identifier.DOIIdentifierProvider
>>   * bean org.dspace.identifier.doi.DOIConnector
>>
>> and adjusted the crosswalk
>> [dspace]/config/crosswalks/DIM2DataCite.xsl
>> You can test the crosswalk with
>> [dspace]/bin/dspace dsrun 
>> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite  
>> [output-file]
>>
>> newly added items will get an entry in the doi table.
>> You can check what is in your doi table with
>> SELECT * from doi;
>>
>> If you have already existing items you got to retrospectively create
>> the entries in the table.
>> We did this by manipulating the database (usual warning about backup):
>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status) 
>> SELECT nextval('doi_seq'), 
>> concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 
>> 7
>> FROM item WHERE in_archive=true and item_id not in (select resource_id from 
>> doi where resource_type_id=2);
>>
>> and then running the doi-organiser.
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>>
>> Am 22.10.2018 um 12:55 schrieb Paul Münch:
>>> Hello,
>>>
>>> I figured out that the Proxy configuration is not the problem. Somehow
>>> it is not possible to do anything with the 'doi-organiser'. Everytime I
>>> tried to reserve, register or update all for test purposes, I got these
>>> error message: There are no objects in database that could be ...
>>> I configured our DSpace-Instance how descriebed in the documentation.
>>> The database connection is fine. Can anybody help me?
>>>
>>> Thanks in advance and kind regards,
>>>
>>> Paul Münch
>>>
>>> Am 19.10.18 um 14:20 schrieb Paul Münch:
 Hello,

 we have a problem with the 'doi-organiser'-tool via our proxy server.
 All proxy configuration works fine, e.g. OAI, REST or command line
 programms like 'wget'. But if we use the 'doi-organiser', we get a
 'Connection timed out'. All DSpace-DOI configuration are successfully
 tested on VMs without proxy. So there is no problem.
 In our Java environment the proxy parameters are all set and are in use
 during the 'doi-organiser' ( I check it with 'jps -lvm' ). Additionally
 I added 'System.setProperty(...)' to 'DataCiteConnector.java' - without
 success.
 I have no idea how to solve this issue and hope someone of you could help.

 Thanks in advance and kind regards,

 Paul Münch

>>
>> -- 
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> Universitätsbibliothek
>> Vogelpothsweg 76
>> 44227 Dortmund
>>
>> Tel.: +49 231-755 40 43
>> Fax: +49 231-755 40 32
>> claudia.juer...@tu-dortmund.de
>> www.ub.tu-dortmund.de
>> /Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich.
>> Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht
>> der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte
>> den Absender und vernichten Sie diese Mail. Vielen Dank.
>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung
>> eines solchen Schriftstücks per Telefax erfolgen.
>>
>> Important note: The information included in this e-mail is
>> confidential. It is solely intended for the recipient. If yo

[dspace-tech] Retrieve a bibliographical hierarchy using SWORD-only?

[Stefan Kombrink]

Dear community,

 after the latest success in our SWORD-related DSpace Quests :D there
remains one last challenge:

Obtaining a community/subcommunity/collection hierarchy within the
service document.

To us this seems impossible. Actually the only thing missing is a
definable unique path for each collection of the service document since
names are often similar, e.g. "Research Data", "Publications", ...

Currently we retrieve this hierarchy using REST but some institutions
seem reluctant enabling it. Is there a way to bootleg this data through
the service document?

Any suggestions / ideas?

Thanks in advance & appreciation
Stefan

-- 
Stefan Kombrink
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abteilung Informationsmedien
+49-731-50-31482

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Remove restrictions on entire collection with items

[Lewatle Johannes Phaladi]

Dear Claudia,

Thank you very much, I have tested after making the necessary settings on 
JSPUI interface and the items are accessible for anonymous user.

Regards,
Lewatle  

On Tuesday, 23 October 2018 15:32:15 UTC+2, Lewatle Johannes Phaladi wrote:
>
> Dear DSpace Team,
>
> I have collection with more than 300 items which are closed for anonymous 
> access, I cant go manually one by one changing individual items 
> authorization policy to allow anonymous user access. Please share with me 
> how to remove restrictions on collection for public / anonymous access.
>
> Regards,
> Lewatle 
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Retrieve a bibliographical hierarchy using SWORD-only?

[Stefan Kombrink]

Okay, I will update this question by myself:

 it seems possible to configure SWORD to deliver communities instead of
collections:

swordv2-server.expose-communities = true [local.cfg]

Then, I am able to retrieve a list of service documents for their
collections.

This way it should be possible to build a community-collection
hierarchy. It just remains unclear what will happen for repositories
that make use of sub-communities and have a deeper hierarchy level e.g.
bibliography-community-subcommunity-collection.

Could anyone please elaborate on that?
Would be amazing if I could cover all functionality with SWORD-only!

Regards Stefan

On 10/24/18 2:20 PM, Stefan Kombrink wrote:
> Dear community,
> 
>  after the latest success in our SWORD-related DSpace Quests :D there
> remains one last challenge:
> 
> Obtaining a community/subcommunity/collection hierarchy within the
> service document.
> 
> To us this seems impossible. Actually the only thing missing is a
> definable unique path for each collection of the service document since
> names are often similar, e.g. "Research Data", "Publications", ...
> 
> Currently we retrieve this hierarchy using REST but some institutions
> seem reluctant enabling it. Is there a way to bootleg this data through
> the service document?
> 
> Any suggestions / ideas?
> 
> Thanks in advance & appreciation
> Stefan
> 

-- 
Stefan Kombrink
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abteilung Informationsmedien
+49-731-50-31482

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Retrieve a bibliographical hierarchy using SWORD-only?

[Tim Donohue]

Hi Stefan,

I'm not sure this is possible, as the SWORD protocol itself defines the
structure of  SWORD service documents.  Service Documents only really list
locations that SWORD is able to deposit into. They really aren't designed
to display hierarchy.

Here's more on the service document format from the SWORD protocol
documentation itself:
* SWORDv1:
http://www.ukoln.ac.uk/repositories/digirep/index/SWORD_APP_Profile_1.2#8._Service_Documents
* SWORDv2:
http://swordapp.github.io/SWORDv2-Profile/SWORDProfile.html#protocoloperations_retreivingservicedocument


I guess it *might* be possible to tweak the DSpace SWORD implementation
code to stuff the hierarchy into the Collection "title" in SWORD -- e.g.
"Top Community > Sub Community > Collection".  But, we don't have a way to
support that in out-of-the-box DSpace, so you'd have to change the code.
If this seems like a reasonable solution, I think you'd basically need to
update the CollectionCollectionGenerator (for either SWORDv1 or v2) to
determine the full hierarchy of names, and then save those as the "title"
here:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-sword/src/main/java/org/dspace/sword/CollectionCollectionGenerator.java#L73


- Tim

On Wed, Oct 24, 2018 at 8:17 AM Stefan Kombrink 
wrote:

> Okay, I will update this question by myself:
>
>  it seems possible to configure SWORD to deliver communities instead of
> collections:
>
> swordv2-server.expose-communities = true [local.cfg]
>
> Then, I am able to retrieve a list of service documents for their
> collections.
>
> This way it should be possible to build a community-collection
> hierarchy. It just remains unclear what will happen for repositories
> that make use of sub-communities and have a deeper hierarchy level e.g.
> bibliography-community-subcommunity-collection.
>
> Could anyone please elaborate on that?
> Would be amazing if I could cover all functionality with SWORD-only!
>
> Regards Stefan
>
> On 10/24/18 2:20 PM, Stefan Kombrink wrote:
> > Dear community,
> >
> >  after the latest success in our SWORD-related DSpace Quests :D there
> > remains one last challenge:
> >
> > Obtaining a community/subcommunity/collection hierarchy within the
> > service document.
> >
> > To us this seems impossible. Actually the only thing missing is a
> > definable unique path for each collection of the service document since
> > names are often similar, e.g. "Research Data", "Publications", ...
> >
> > Currently we retrieve this hierarchy using REST but some institutions
> > seem reluctant enabling it. Is there a way to bootleg this data through
> > the service document?
> >
> > Any suggestions / ideas?
> >
> > Thanks in advance & appreciation
> > Stefan
> >
>
> --
> Stefan Kombrink
> Universität Ulm
> Kommunikations- und Informationszentrum (kiz)
> Abteilung Informationsmedien
> +49-731-50-31482 <+49%20731%205031482>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Authorization policy of collection not opening for previously submitted items on DSpace 6.2

[Tim Donohue]

Hi Lewatle,

As you've seen, Permission changes at the Collection level do not
automatically get inherited to Items already in that Collection.  Each
individual object has separate permissions, and Items only inherit
permissions at the point at which they are submitted.

However, if you need to manage/change permissions in bulk, you can do so
via the DSpace "Advanced Policy Manager" tool.  Here's a video on how to
use it: https://youtu.be/PFlq-yGSPY4

It looks to not be well documented in the official Documentation at this
time (or I'm not finding it). But here's some guidelines wrote up by the
DSpaceDirect team:
https://wiki.duraspace.org/display/DSpaceDirectKB/Getting+Started+How-To#GettingStartedHow-To-Bulk/BatchPermissionsChanges(Advanced
)

- Tim

On Wed, Oct 24, 2018 at 2:47 AM Lewatle Johannes Phaladi 
wrote:

> Dear DSpace Team,
>
> I have edited authorization policy directly on collection and added Read,
> Default_Bitstream_Read and Default_Item Read for Anonymous user, I have
> then tried to open older submitted items and they are still restricted for
> non-logged in users, i have done test submission to check if new items are
> accessible to anonymous users and yes they are accessible, I would like to
> know if there is way to open previously submitted items under collection
> without changing policy on item one by one.
>
> Regards,
> Lewatle
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Can not add a user

[Chin U. Kim]

Hello All,

When attempting to add a user to DSpace 6.x I am met with;


Exception: bad_dublin_core schema=eperson.language.null. Metadata field 
does not exist!
java.sql.SQLException: bad_dublin_core schema=eperson.language.null. 
Metadata field does not exist!
at 
org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:210)
at 
org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:299)
at 
org.dspace.content.DSpaceObjectServiceImpl.setMetadataSingleValue(DSpaceObjectServiceImpl.java:396)
at org.dspace.eperson.EPerson.setLanguage(EPerson.java:175)
at org.dspace.eperson.EPersonCLITool.cmdAdd(EPersonCLITool.java:176)
at org.dspace.eperson.EPersonCLITool.main(EPersonCLITool.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)


I can delete a user but can not modify or add.

I do not know how to correct this.

Thank you in advance for your assistance.

Best,
Chin

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] DSpace 6.3 REST-API stopped working in Ubuntu 18.04 and 18.10

[Christoph Weber]

Hi Tim,

thanks for your answer.
I just did a fresh install of everything. Fresh ubuntu 18.10 with java 8, 
fresh postgres 10 database and fresh DSpace 6.3 following the install 
instructions.
Just to rule out potential problems caused by ubuntu updates.

REST-API is still failing to start. Normal DSpace works as expected.

When I build dspace with mvn package -Dmirage2.on=true, I get the following 
warning:

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter: 
o  'org.glassfish.hk2.external:bean-validator:jar:*'

In [dspace]/log/dspace-2018-10-24.log I get the following error when I try 
to start the REST-API webapp:

2018-10-24 15:14:02,820 FATAL org.dspace.core.Context @ Cannot obtain the 
bean which provides a database connection. Check previous entries in the 
dspace.log
to find why the db failed to initialize. The schema validator returned: 
Error activating Bean Validation integration

Previous entries don't really give me any clues what might be wrong:

2018-10-24 15:18:01,501 INFO  org.dspace.statistics.SolrLoggerServiceImpl @ 
solr-statistics.spidersfile:null 
2018-10-24 15:18:01,502 INFO  org.dspace.statistics.SolrLoggerServiceImpl @ 
solr-statistics.server:http://myserver.de:8080/solr/statistics 
2018-10-24 15:18:01,502 INFO  org.dspace.statistics.SolrLoggerServiceImpl @ 
usage-statistics.dbfile:/opt/dspace/config/GeoLite2-City.mmdb 
2018-10-24 15:18:01,700 INFO  org.dspace.statistics.SolrLoggerServiceImpl @ 
useProxies=false 
2018-10-24 15:18:01,930 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
Loading Flyway DB migrations from: filesystem:/opt/dspace/etc/postgres, 
classpath:org.
dspace.storage.rdbms.sqlmigration.postgres, 
classpath:org.dspace.storage.rdbms.migration 
2018-10-24 15:18:01,946 INFO 
 org.flywaydb.core.internal.util.VersionPrinter @ Flyway 4.0.3 by Boxfuse 
2018-10-24 15:18:01,959 INFO 
 org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: 
jdbc:postgresql://localhost:5432/dspace (PostgreSQL 10.5) 
2018-10-24 15:18:02,040 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
DSpace database schema is up to date 
2018-10-24 15:18:02,055 INFO  org.dspace.event.EventServiceImpl @ 
EventService dispatcher pool initialized 
2018-10-24 15:18:02,193 INFO  org.hibernate.annotations.common.Version @ 
HCANN01: Hibernate Commons Annotations {4.0.2.Final} 
2018-10-24 15:18:02,199 INFO  org.hibernate.Version @ HHH000412: Hibernate 
Core {4.2.21.Final} 
2018-10-24 15:18:02,201 INFO  org.hibernate.cfg.Environment @ HHH000206: 
hibernate.properties not found 
2018-10-24 15:18:02,202 INFO  org.hibernate.cfg.Environment @ HHH21: 
Bytecode provider name : javassist 
2018-10-24 15:18:02,227 INFO  org.hibernate.cfg.Configuration @ HHH44: 
Configuring from URL: file:/opt/dspace/config/hibernate.cfg.xml 
2018-10-24 15:18:02,272 INFO  org.hibernate.cfg.Configuration @ HHH41: 
Configured SessionFactory: null 
2018-10-24 15:18:02,455 INFO  org.hibernate.dialect.Dialect @ HHH000400: 
Using dialect: 
org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect 
2018-10-24 15:18:02,468 INFO 
 org.hibernate.engine.jdbc.internal.LobCreatorBuilder @ HHH000424: 
Disabling contextual LOB creation as createClob() method thre
w error : java.lang.reflect.InvocationTargetException 
2018-10-24 15:18:02,477 INFO  org.hibernate.type.BasicTypeRegistry @ 
HHH000270: Type registration [pg-uuid] overrides previous : 
org.hibernate.type.PostgresU
UIDType@376076dd 
2018-10-24 15:18:02,477 INFO  org.hibernate.type.BasicTypeRegistry @ 
HHH000270: Type registration [java.util.UUID] overrides previous : 
org.hibernate.type.UU
IDBinaryType@7f4b7480 
2018-10-24 15:18:02,713 INFO 
 org.hibernate.engine.transaction.internal.TransactionFactoryInitiator @ 
HHH000399: Using default transaction strategy (direct J
DBC transactions) 
2018-10-24 15:18:02,719 INFO 
 org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory @ HHH000397: 
Using ASTQueryTranslatorFactory 
2018-10-24 15:18:02,764 WARN  net.sf.ehcache.CacheManager @ Creating a new 
instance of CacheManager using the diskStorePath "/tmp" which is already 
used by a
n existing CacheManager. 
The source of the configuration was 
net.sf.ehcache.config.generator.ConfigurationSource$URLConfigurationSource@1a477234.
 

The diskStore path for this CacheManager will be set to 
/tmp/ehcache_auto_created_1540394282764. 
To avoid this warning consider using the CacheManager factory methods to 
create a singleton CacheManager or specifying a separate ehcache 
configuration (ehca
che.xml) for each CacheManager instance. 
2018-10-24 15:18:02,793 INFO  org.hibernate.cache.spi.UpdateTimestampsCache 
@ HHH000250: Starting update timestamps cache at region: 
org.hibernate.cache.spi.
UpdateTimestampsCache 
2018-10-24 15:18:02,797 INFO 
 org.hibernate.cache.internal.StandardQueryCache @ HHH000248: Starting 
query cache at region: org.hibernate.cache.internal.Stand
ardQueryCache 
2018-10-24 15:18:02,829 INFO  org.hibernate.valida

[dspace-tech] Re: Can not add a user

[Chin U. Kim]

I added language to the eperson metadata schema and it resolved the issue.

Not sure how all these other user accounts were created without it... but.. 
it works now.

On Wednesday, October 24, 2018 at 10:24:50 AM UTC-4, Chin U. Kim wrote:
>
> Hello All,
>
> When attempting to add a user to DSpace 6.x I am met with;
>
>
> Exception: bad_dublin_core schema=eperson.language.null. Metadata field 
> does not exist!
> java.sql.SQLException: bad_dublin_core schema=eperson.language.null. 
> Metadata field does not exist!
> at 
> org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:210)
> at 
> org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:299)
> at 
> org.dspace.content.DSpaceObjectServiceImpl.setMetadataSingleValue(DSpaceObjectServiceImpl.java:396)
> at org.dspace.eperson.EPerson.setLanguage(EPerson.java:175)
> at 
> org.dspace.eperson.EPersonCLITool.cmdAdd(EPersonCLITool.java:176)
> at org.dspace.eperson.EPersonCLITool.main(EPersonCLITool.java:72)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
> at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>
>
> I can delete a user but can not modify or add.
>
> I do not know how to correct this.
>
> Thank you in advance for your assistance.
>
> Best,
> Chin
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] How to hide 32-characher reference from Community group name

[Sharon D]

Hi.   I'm new to Dspace and have recently set up Dspace v6.3  using the 
Mirage theme (xmlui). 
When I want to edit or add a group, the system-generated name includes a 
32-character reference and there is also a reference to an ID number.  

Is there some way to hide these references or to customise them to make 
them shorter?  
Or maybe i've just missed configuring something during the setup which is 
why these references are displayed this way?
NB I can't change the group name using the Change group name field as it is 
"greyed out" 

I would appreciate any help as I've looked through the dspace.cfg file and 
can only see how I can change the Handle ID reference.

[image: ID in group names.JPG]



-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] How to hide 32-character references from Community group name

[Sharon D]

Hi.   I'm new to Dspace and have recently set up Dspace v6.3  using the 
Mirage theme (xmlui).
When I want to edit or add a group, the system-generated name includes a 
32-character reference and also a reference to an ID number
eg  Group Editor: COMMUNITY_67aaab4c-810e-47a4-84e3-6ed26be36a7b_ADMIN (id: 
25645f96-0901-486f-9855-e9c9d3691ef6)

Is there some way to hide these references or to customise them to make 
them shorter? 
Or maybe i've just missed configuring something during the setup which is 
why these references are displayed this way?
I would appreciate any help as I've looked through the dspace.cfg file and 
can only see how I can change the Handle ID reference.


-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] View Statistics links not working

[wlrutherford]

I made some progress and lost a little ground at the same time. First I 
verified that all of the statistics config files were
watching the same port:

*/dspace/config/modules/solr-statistics.cfg*
server = http://localhost:8080/solr/statistics

*/dspace/config/modules/oai.cfg*
solr.url=http://localhost:8080/solr/oai

*/dspace/config/modules/discovery.cfg*
 search.server = http://localhost:8080/solr/search

*/dspace/config/dspace.cfg*
solr.authority.server=https://dspace36a.library.uaf.edu:8080/solr/authority
 choices.plugin.dc.contributor.author = SolrAuthorAuthority
 choices.presentation.dc.contributor.author = authorLookup
 authority.controlled.dc.contributor.author = true

# Still trying to get publicly viewable statistics. I was sure these had 
been set
# in the past but I can't find them in this file now. Perhaps solr config 
file.  10/15/18 WLR
report.public = true
statistics.item.authorization.admin = false

# 10/19/18 WLR // updated 10/24/18 WLR
#solr.server = http://localhost:8080/solr
solr.server = http://localhost:8080/solr/statistics


*/etc/httpd/conf.d/vhosts.conf*

### Redirect insecure default port to secure port 443
ServerAdmin uaf-library-it-d...@alaska.edu
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}



### secure httpd server listening on port 443.

ServerAdmin uaf-library-it-d...@alaska.edu
RewriteEngine On
# There's probably a better way to do this
RewriteCond %{REQUEST_URI} "^/solr"  
[NC]
RewriteCond %{REQUEST_URI} "^/statistic"[NC]
RewriteCond %{REQUEST_URI} "^/statistics-home"[NC]
RewriteCond %{REQUEST_URI} "^/search-statistics"  [NC]
RewriteCond %{REQUEST_URI} "^/workflow-statistics"   [NC]
RewriteRule (.*) http://%{HTTP_HOST}:8080%{REQUEST_URI} [R,L]

DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-https-error_log
CustomLog logs/dspace36a.library.uaf.edu-https-access_log 
combinedssl
RewriteLog logs/dspace36a-rewrite

Include conf.d/ssl.include
Include conf.d/ssl.include.star
### ^ these point to a file which specifies where the ssl 
certificates
###   live on the host.

#   ProxyPass / http://127.0.0.1:8080/  retry=10 connectiontimeout=5
ProxyPass /  http://127.0.0.1:443/retry=10 
connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 8080

#timeout=300

#   ProxyPassReverse /  http://127.0.0.1:8080/  retry=10
ProxyPassReverse /   http://127.0.0.1:443/retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to 
look
###   like they're coming from httpd.

ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the 
client and
### pass it on to tomcat.

#SSLUseStapling on
### Added due to error when starting apache.  Dayne Ellanna




#
### Redirect insecure ports to secure port 443
ServerAdmin uaf-library-it-d...@alaska.edu
RewriteEngine On
RewriteCond %{HTTPS} on
RewriteRule (.*) http://%{HTTP_HOST}:8080/%{REQUEST_URI} [R,L]
DocumentRoot /dspace/webapps/xmlui
ServerName dspace36a.library.uaf.edu
ServerAlias scholarworks

ErrorLog logs/dspace36a.library.uaf.edu-error_log
CustomLog logs/dspace36a.library.uaf.edu-access_log common
RewriteLog logs/dspace36a-rewrite

ProxyPass / http://127.0.0.1:8080/  retry=10 connectiontimeout=5
### ^ this tells httpd to redirect it's / to localhost port 443

#timeout=300
ProxyPassReverse / http://127.0.0.1:8080/  retry=10
### ^ this tells httpd that tomcat's url's should be rewritten to 
look
###   like they're coming from httpd.

#   ProxyPreserveHost On
### ^ this tells httpd to keep the Host: information from the 
client and
### pass it on to tomcat.



*[tomcat]/conf/server.xml*

 

So I managed to break both ports 80 and 443 but, amazingly port 8080 works 
like a charm
and gives the statistics I've been trying to see for many weeks! I suspect 
the new problem
is in the vhosts.conf file but haven't yet caught what's going wrong.
http://dspace36a.library.uaf.edu:8080/

The stats links now work for the whole site (Home Page) and for individual 
items, although
I'm not entirely sure the single item stats are working completely 
correctly since I haven't
seen them working until now and there are often blanks within the returned 
information.

=



On Friday, October 19, 2018 at 1:10:05 PM UTC-8, wlruth...@alaska.edu wrote:
>
>
> I set "solr

Re: [dspace-tech] How to hide 32-character references from Community group name

[Paul Münch]

Hello,

unfortunately you can't configure these behaviour. Changes have to make
inside the code.

For example take a look into the Method 'createAdministrators':
https://github.com/DSpace/DSpace/blob/bd9bd233b762762d3866a653ff95fc598cc723c5/dspace-api/src/main/java/org/dspace/content/CollectionServiceImpl.java#L496
.

The collection ID is used to set the group's name. It's the same in
'createSubmitters' and 'createWorkflowGroup'.

Kind regards,

Paul Münch

Am 25.10.18 um 02:51 schrieb Sharon D:
> Hi.   I'm new to Dspace and have recently set up Dspace v6.3  using
> the Mirage theme (xmlui).   
> When I want to edit or add a group, the system-generated name includes
> a 32-character reference and also a reference to an ID number
> eg  Group Editor: COMMUNITY_67aaab4c-810e-47a4-84e3-6ed26be36a7b_ADMIN
> (id: 25645f96-0901-486f-9855-e9c9d3691ef6)
>
> Is there some way to hide these references or to customise them to
> make them shorter?
> Or maybe i've just missed configuring something during the setup which
> is why these references are displayed this way?
> I would appreciate any help as I've looked through the dspace.cfg file
> and can only see how I can change the Handle ID reference.
>
>
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 post to this group, send email to dspace-tech@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.

-- 
Philipps-Universität Marburg | UB 
Digitale Dienste | Deutschhausstraße 9 | D018
Tel. +49 06421 28-24624  
--

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature