[dspace-tech] Re: Total records in the news-xmlui

2020-09-14 Thread Ayuka Phanuel
Any help with this is highly appreciated.



On Sat, Sep 12, 2020 at 4:29 PM Ayuka Phanuel 
wrote:

> I want to add the total number of records to the news-xmlui. Is this data
> in the repository meta and how can I add it to the page ?
>
> For example:
>
>
> http://di.tamu.edu/DRI/1.0/"; xmlns:i18n="
> http://apache.org/cocoon/i18n/2.1"; version="1.1">
> 
>  class="white-box">
> 
> My Dspace
> My dspace description
>   *  {{7000 records}}*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwwA1m7YKpynpZKmheqNugYA65EkPpHA5%3DGho%3D0eCx6V1A%40mail.gmail.com.


[dspace-tech] Total records in the news-xmlui

2020-09-12 Thread Ayuka Phanuel
I want to add the total number of records to the news-xmlui. Is this data
in the repository meta and how can I add it to the page ?

For example:


http://di.tamu.edu/DRI/1.0/"; xmlns:i18n="
http://apache.org/cocoon/i18n/2.1"; version="1.1">



My Dspace
My dspace description
  *  {{7000 records}}*











-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwzJWgBu2Crf9Hu9BmjgKh3OHqRgdRKviKNB4T1sKFoJtA%40mail.gmail.com.


Re: [dspace-tech] rror creating submission forms: org.xml.sax.SAXException: Required field input-type missing on page 2 of form traditional

2020-07-06 Thread Ayuka Phanuel
Hi David.
Check the input-forms.xml inside the  tag. You seem to
have forgotten to add *input type* to a form field.
org.dspace.app.util.DCInputsReaderException: Error creating submission
forms: org.xml.sax.SAXException: Required field input-type missing on page
2 of form traditional

*Kind Regards, *
*Phanuel Ayuka.*


On Mon, Jul 6, 2020 at 6:29 PM David Avila  wrote:

> Dear all
> Can someone help me with this error, I was modifying the input-form and it
> generates the following error
>
> Java stacktrace: org.dspace.app.util.DCInputsReaderException: Error
> creating submission forms: org.xml.sax.SAXException: Required field
> input-type missing on page 2 of form traditional at
> org.dspace.app.util.DCInputsReader.buildInputs(DCInputsReader.java:133) at
> org.dspace.app.util.DCInputsReader.(DCInputsReader.java:102) at
> org.dspace.submit.step.DescribeStep.getInputsReader(DescribeStep.java:446)
> at
> org.dspace.app.xmlui.aspect.submission.submit.DescribeStep.setup(DescribeStep.java:130)
> at
> org.dspace.app.xmlui.aspect.submission.StepTransformer.setup(StepTransformer.java:131)
> at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy222.setup(Unknown Source) at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:356)
> at
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:710)
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:466)
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.prepareInternal(AbstractProcessingPipeline.java:480)
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy217.prepareInternal(Unknown Source) at
> org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:292)
> at
> org.apache.cocoon.components.source.impl.SitemapSource.(SitemapSource.java:148)
> at
> org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:62)
> at
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:153)
> at
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:183)
> at org.apache.cocoon.generation.FileGenerator.setup(FileGenerator.java:99)
> at
> org.dspace.app.xmlui.cocoon.AspectGenerator.setup(AspectGenerator.java:81)
> at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy218.setup(Unknown Source) at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:343)
> at
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:710)
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:466)
> at
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.prepareInternal(AbstractProcessingPipeline.java:480)
> at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at com.sun.proxy.$Proxy217.prepareInternal(Unknown Source) at
> org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:292)
> at
> org.apache.cocoon.components.source.impl.SitemapSource.(SitemapSource.java:148)
> at
> org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:62)
> at
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:153)
> at
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:183)
> at org.apache.cocoon.generation.FileGenerator.setup(FileGenerator.java:99)
> at
> org.dspace.app.xmlui.cocoon.AspectGenerator.setup(AspectGenerator.java:81)
> at sun.reflect.GeneratedMethodAccessor108.invoke

Re: [dspace-tech] Problems with uploading files using REST API.

2020-03-12 Thread Ayuka Phanuel
Python 3 , DSpace 6.3

On Thu, 12 Mar 2020, 17:04 gıyaseddin tanrıkulu,  wrote:

> No luck, same problem.
> What version of DSpace are you using?
>
> On Saturday, March 7, 2020 at 12:48:20 PM UTC+3, Ayuka Phanuel wrote:
>>
>> This is what i use:
>> And is working fine.
>>
>> with open(directory, 'rb') as f:
>> file_response = requests.post(rest_items_api_link + item_uuid + 
>> "/bitstreams",
>>   files={file_name: f},
>>   params={'name': file_name},
>>   headers={'Content-Type': 
>> 'multipart/form-data'},
>>   cookies={"JSESSIONID": "x"})
>> print(file_response.text)
>>
>>
>>
>>
>> On Fri, Mar 6, 2020 at 5:26 PM gıyaseddin tanrıkulu 
>> wrote:
>>
>>> Hi there,
>>> I am trying to upload files using REST API but for some reason, when I
>>> download these files, I see
>>> a content-disposition header along with a number that is on top and
>>> bottom. Here's an example:
>>>
>>>
>>> --3920b9ce37f4e3292af6d8081aa02501
>>>
>>> 1 Content-Disposition: form-data; name="file"; filename="TODO"
>>>
>>> ...file content...
>>>
>>> --3920b9ce37f4e3292af6d8081aa02501--
>>>
>>> I tried to send this with and without header, but regardless the outcome
>>> is same. I suspect that upon saving
>>> these files, DSpace mistakenly adds this header to file content.
>>>
>>> I tried to upload using python and bash, I'm adding the code snippets in
>>> case if they provide any useful information.
>>>
>>> *Python:*
>>> PARAMS = {'Accept': "application/json",
>>>   'Content-Type': "application/json"}
>>>
>>> def upload_file(file_path, item_uuid, cookie):
>>> """ Upload file to a DSpace item.
>>>
>>> Arguments:
>>> file  -- The path of file to upload.
>>> item_uuid -- The item UUID in the rest api.
>>> cookie-- JSESSIONID for authentication.
>>> """
>>>
>>> # Add JSESSIONID to request header
>>> parameters = PARAMS
>>> parameters["Cookie"] = "JSESSIONID=" + cookie
>>> parameters["Content-Type"] = "multipart/form-data"
>>>
>>> # Prepare files dict for request
>>> file = open(file_path, 'rb')
>>> files = {'file': file}
>>>
>>> response = requests.post(url=URL + "/rest/items/" + item_uuid +
>>> "/bitstreams?name=" + os.path.basename(file.name),
>>>  files=files, headers=parameters)
>>> pdb.set_trace()
>>>
>>> file.close()
>>>
>>>
>>>
>>> *Bash:*
>>> curl -k -v -4 --trace dspace.log --cookie
>>> "JSESSIONID=2C20ADE1EEC3EA7E225C32884A31EC59" -H "Accept:
>>> application/json" -X POST "
>>> http://localhost:8080/rest/items/46309f1d-c5fd-4142-80d7-3c850b5f955b/bitstreams?name=test.sh
>>> " -T test.sh
>>>
>>>
>>>
>>> Here's the information that you might need:
>>>
>>> *OS*:
>>> Manjaro Linux 19.0.2
>>>
>>> *Tomcat:*
>>> Server version: Apache Tomcat/8.5.51
>>> Server built:   Feb 5 2020 22:26:25 UTC
>>> Server number:  8.5.51.0
>>> OS Name:Linux
>>> OS Version: 5.4.23-1-MANJARO
>>> Architecture:   amd64
>>> JVM Version:1.8.0_242-b08
>>> JVM Vendor: Oracle Corporation
>>>
>>> *Maven:*
>>> Apache Maven 3.6.3 (NON-CANONICAL_2019-11-27T20:26:29Z_root)
>>> Maven home: /opt/maven
>>> Java version: 1.8.0_242, vendor: Oracle Corporation, runtime:
>>> /usr/lib/jvm/java-8-openjdk/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "5.4.23-1-manjaro", arch: "amd64", family:
>>> "unix"
>>>
>>> *Ant:*
>>> Apache Ant(TM) version 1.10.7 compiled on September 10 2019
>>>
>>> *DSpace:*
>>> DSpace version:  6.3
>>>   SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
>>> SCM branch: 

Re: [dspace-tech] PDF file download and view setting in Dspace Xmlui 6.3

2020-03-12 Thread Ayuka Phanuel
What will prevent people from taking photos or screenshot of the file they
can view and print later?
The best solution in my opinion is to restrict files access (read
permissions) using bitstream embargo policies.

On Thu, 12 Mar 2020, 17:04 Umeshwar Rai,  wrote:

> Any one please help
>
> How do i disable downloading and print button from browser when the pdf
> file is open in browser on click of view/open button
>
> Regards,
>
> Umeshwar
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/41d57fda-0200-4f43-bd74-c4db3fbcadcb%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwwK-RB_Xa4EifoMjBL%2BiZkTgKU8VBGz%3D-CvLZ2nEVr8Sw%40mail.gmail.com.


Re: [dspace-tech] Problems with uploading files using REST API.

2020-03-07 Thread Ayuka Phanuel
This is what i use:
And is working fine.

with open(directory, 'rb') as f:
file_response = requests.post(rest_items_api_link + item_uuid +
"/bitstreams",
  files={file_name: f},
  params={'name': file_name},
  headers={'Content-Type':
'multipart/form-data'},
  cookies={"JSESSIONID": "x"})
print(file_response.text)




On Fri, Mar 6, 2020 at 5:26 PM gıyaseddin tanrıkulu 
wrote:

> Hi there,
> I am trying to upload files using REST API but for some reason, when I
> download these files, I see
> a content-disposition header along with a number that is on top and
> bottom. Here's an example:
>
>
> --3920b9ce37f4e3292af6d8081aa02501
>
> 1 Content-Disposition: form-data; name="file"; filename="TODO"
>
> ...file content...
>
> --3920b9ce37f4e3292af6d8081aa02501--
>
> I tried to send this with and without header, but regardless the outcome
> is same. I suspect that upon saving
> these files, DSpace mistakenly adds this header to file content.
>
> I tried to upload using python and bash, I'm adding the code snippets in
> case if they provide any useful information.
>
> *Python:*
> PARAMS = {'Accept': "application/json",
>   'Content-Type': "application/json"}
>
> def upload_file(file_path, item_uuid, cookie):
> """ Upload file to a DSpace item.
>
> Arguments:
> file  -- The path of file to upload.
> item_uuid -- The item UUID in the rest api.
> cookie-- JSESSIONID for authentication.
> """
>
> # Add JSESSIONID to request header
> parameters = PARAMS
> parameters["Cookie"] = "JSESSIONID=" + cookie
> parameters["Content-Type"] = "multipart/form-data"
>
> # Prepare files dict for request
> file = open(file_path, 'rb')
> files = {'file': file}
>
> response = requests.post(url=URL + "/rest/items/" + item_uuid +
> "/bitstreams?name=" + os.path.basename(file.name),
>  files=files, headers=parameters)
> pdb.set_trace()
>
> file.close()
>
>
>
> *Bash:*
> curl -k -v -4 --trace dspace.log --cookie
> "JSESSIONID=2C20ADE1EEC3EA7E225C32884A31EC59" -H "Accept:
> application/json" -X POST "
> http://localhost:8080/rest/items/46309f1d-c5fd-4142-80d7-3c850b5f955b/bitstreams?name=test.sh
> " -T test.sh
>
>
>
> Here's the information that you might need:
>
> *OS*:
> Manjaro Linux 19.0.2
>
> *Tomcat:*
> Server version: Apache Tomcat/8.5.51
> Server built:   Feb 5 2020 22:26:25 UTC
> Server number:  8.5.51.0
> OS Name:Linux
> OS Version: 5.4.23-1-MANJARO
> Architecture:   amd64
> JVM Version:1.8.0_242-b08
> JVM Vendor: Oracle Corporation
>
> *Maven:*
> Apache Maven 3.6.3 (NON-CANONICAL_2019-11-27T20:26:29Z_root)
> Maven home: /opt/maven
> Java version: 1.8.0_242, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/java-8-openjdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.4.23-1-manjaro", arch: "amd64", family:
> "unix"
>
> *Ant:*
> Apache Ant(TM) version 1.10.7 compiled on September 10 2019
>
> *DSpace:*
> DSpace version:  6.3
>   SCM revision:  813800ce1736ec503fdcfbee4d86de836788f87c
> SCM branch:  UNKNOWN
> OS:  Linux(amd64) version 5.4.23-1-MANJARO
>   Applications:
> REST at http://localhost:8080/xmlui
> XMLUI at http://localhost:8080/xmlui
> REST at http://localhost:8080/xmlui
> XMLUI at http://localhost:8080/xmlui
> REST at http://localhost:8080/xmlui
> XMLUI at http://localhost:8080/xmlui
>  Discovery:  enabled.
>JRE:  Oracle Corporation version 1.8.0_242
>Ant version:  Apache Ant(TM) version 1.10.7 compiled on September 10
> 2019
>  Maven version:  3.3.9
>  DSpace home:  /dspace
>
> Any help would be appreciated ^_^
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/20fc0555-370d-4ab7-9957-f4575431f65c%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on t

Re: [dspace-tech] 2 issues after setting up DSpace 6.3

2020-03-07 Thread Ayuka Phanuel
You might need to log in to your Gmail account through a web browser and
enable access through less secure apps for this to work if you
haven't already.



On Sat, Mar 7, 2020 at 11:18 AM Ashim Kapoor 
wrote:

> Hi there,
>
> When I switch to port 465, it allows submission but not user registration.
>
> Here is the output:-
>
>
> root@DSpace:/home/dspace/dspace-install/bin# ./dspace test-email
>
> About to send test email:
>  - To: x...@gmail.com
>  - Subject: DSpace test email
>  - Server: smtp.gmail.com
>
> Error sending email:
>  - Error: javax.mail.SendFailedException: Send failure
> (javax.mail.MessagingException: Could not connect to SMTP host:
> smtp.gmail.com, port: 465, response: -1)
>
> Please see the DSpace documentation for assistance.
>
>
>
> root@DSpace:/home/dspace/dspace-install/bin#
>
> On Sat, 7 Mar 2020 at 10:39, Ashim Kapoor 
> wrote:
>
>> Dear Ayuka,
>>
>> I switched to port 587.
>>
>> Now I am able to submit an item to a Collection. However I am not able to
>> register a new user. It says "Unable to send email to this address".
>>
>> Also earlier I never mentioned the ports you have mentioned. Why was it
>> working fine earlier without the ports?
>>
>> Please see below:-
>> root@DSpace:/home/dspace/dspace-install/bin# ./dspace test-email
>>
>> About to send test email:
>>  - To: x...@gmail.com
>>  - Subject: DSpace test email
>>  - Server: smtp.gmail.com
>>
>> Error sending email:
>>  - Error: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue
>> a STARTTLS command first. d77sm25077809pfd.109 - gsmtp
>>
>>
>> Please see the DSpace documentation for assistance.
>>
>>
>>
>> root@DSpace:/home/dspace/dspace-install/bin#
>>
>> On Fri, 6 Mar 2020 at 18:06, Ayuka Phanuel 
>> wrote:
>>
>>> I think you need to change the SMTP Port from default to the GMAIL Ports
>>> as below.
>>> Gmail SMTP port (TLS): 587
>>> Gmail SMTP port (SSL): 465
>>>
>>> Port 587 is your best bet.
>>>
>>>
>>>
>>> On Fri, Mar 6, 2020 at 3:17 PM Ashim Kapoor 
>>> wrote:
>>>
>>>> Dear Bram and Adam,
>>>>
>>>> When I do this [dspace]/bin/test-email
>>>>
>>>> I get this :
>>>>
>>>> About to send test email:
>>>>  - To: x...@gmail.com
>>>>  - Subject: DSpace test email
>>>>  - Server: smtp.gmail.com
>>>>
>>>> It is frozen at this place.
>>>>
>>>> The Email section in local.cfg looks like this (the filled in entries
>>>> are denoted by xxx) :-
>>>>
>>>> # SMTP mail server (allows DSpace to send email notifications)
>>>> mail.server = smtp.gmail.com
>>>>
>>>> # SMTP mail server authentication username and password (if required)
>>>> mail.server.username = xxx
>>>> mail.server.password = xxx
>>>>
>>>> # SMTP mail server alternate port (defaults to 25)
>>>> mail.server.port = 25
>>>>
>>>> # From address for mail
>>>> # All mail from the DSpace site will use this 'from' address
>>>> mail.from.address = xxx
>>>>
>>>> # When feedback is submitted via the Feedback form, it is sent to this
>>>> address
>>>> # Currently limited to one recipient!
>>>> feedback.recipient = xxx
>>>>
>>>> # General site administration (Webmaster) e-mail
>>>> mail.admin = xxx
>>>>
>>>> # Recipient for server errors and alerts (defaults to mail.admin)
>>>> #alert.recipient = ${mail.admin}
>>>>
>>>> # Recipient for new user registration emails (defaults to unspecified)
>>>> #registration.notify =
>>>>
>>>> On Thu, 5 Mar 2020 at 21:03, Adan  wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Check your email configuration, or disable it and try again.
>>>>> It can be a bottle-neck if it have bad configuration.
>>>>>
>>>>> Regards
>>>>> Adan
>>>>>
>>>>> Dear all,
>>>>>
>>>>> [1]. When I try to register a new user in the following link :-
>>>>>
>>>>> http://192.100.30.xxx:8080/xmlui/register
>>>>>
>>>>> It is taking a very long time.
>>>>>
>>>>> [2]. When I try

Re: [dspace-tech] 2 issues after setting up DSpace 6.3

2020-03-06 Thread Ayuka Phanuel
I think you need to change the SMTP Port from default to the GMAIL Ports as
below.
Gmail SMTP port (TLS): 587
Gmail SMTP port (SSL): 465

Port 587 is your best bet.



On Fri, Mar 6, 2020 at 3:17 PM Ashim Kapoor 
wrote:

> Dear Bram and Adam,
>
> When I do this [dspace]/bin/test-email
>
> I get this :
>
> About to send test email:
>  - To: x...@gmail.com
>  - Subject: DSpace test email
>  - Server: smtp.gmail.com
>
> It is frozen at this place.
>
> The Email section in local.cfg looks like this (the filled in entries are
> denoted by xxx) :-
>
> # SMTP mail server (allows DSpace to send email notifications)
> mail.server = smtp.gmail.com
>
> # SMTP mail server authentication username and password (if required)
> mail.server.username = xxx
> mail.server.password = xxx
>
> # SMTP mail server alternate port (defaults to 25)
> mail.server.port = 25
>
> # From address for mail
> # All mail from the DSpace site will use this 'from' address
> mail.from.address = xxx
>
> # When feedback is submitted via the Feedback form, it is sent to this
> address
> # Currently limited to one recipient!
> feedback.recipient = xxx
>
> # General site administration (Webmaster) e-mail
> mail.admin = xxx
>
> # Recipient for server errors and alerts (defaults to mail.admin)
> #alert.recipient = ${mail.admin}
>
> # Recipient for new user registration emails (defaults to unspecified)
> #registration.notify =
>
> On Thu, 5 Mar 2020 at 21:03, Adan  wrote:
>
>> Hi
>>
>> Check your email configuration, or disable it and try again.
>> It can be a bottle-neck if it have bad configuration.
>>
>> Regards
>> Adan
>>
>> Dear all,
>>
>> [1]. When I try to register a new user in the following link :-
>>
>> http://192.100.30.xxx:8080/xmlui/register
>>
>> It is taking a very long time.
>>
>> [2]. When I try to submit an item it again takes a very long time.
>>
>> I am running DSpace 6.3 on a Debian 10.3 Virtual Machine with 4 GB of
>> RAM. I have java - adoptopenjdk-8-hotspot-amd64. Postgres 11.7. Tomcat9
>> My /etc/default/tomcat9 has the following lines :
>>
>> JAVA_HOME =/usr/lib/jvm/adoptopenjdk-8-hotspot-amd64
>> JAVA_OPTS="-XX:+UseG1GC -Djava.awt.headless=true -Xmx512M -Xms64M
>> -Dfile.encoding=UTF-8"
>>
>> Can someone please help me ?
>>
>>
>> Thank you,
>> Ashim
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGi%3DKi_6PG2XQywSCmzpnZ6ttBXtPPiarCm7YuHDTpbmA%40mail.gmail.com
>> 
>> .
>>
>>
>>
>>
>> 
>>  Libre
>> de virus. www.avast.com
>> 
>> <#m_6093451944195230599_m_-3374357094633476904_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/39d617ec-d636-54e9-b24d-a396cf1838c9%40gmail.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAGEJAoGvgcBgzrpNgRq8OJrR0ROb23mra%2BVZ1FPA5KjRBpqZNw%40mail.gmail.com
> 
> .
>

-- 
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

Re: [dspace-tech] bitsream name is loaded as null through API from Postman

2020-01-24 Thread Ayuka Phanuel
Alongside the file object in your post, pass the name of the file as
parameter. You can extract the file name from the file object.
In Python, have a look at the snippet below.

requests.post(url,
 files={file_name: file_object},
 params={'name': file_name},
 headers={'Content-Type': 'multipart/form-data'},
cookies={"JSESSIONID": ""})


*Kind Regards, *
*Phanuel Ayuka.*
*Systems Developer - **Android | Django | Java EE | ODK Aggregate | PHP*


On Fri, Jan 24, 2020 at 4:32 PM Ponniah MANIKANDAN D <
ponniahmanikan...@gmail.com> wrote:

>  When I try to upload a file to bistream using API, I did POST from
> postman adding the file under body. The file  is successfully uploaded, but
> the name is null.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/7cf4daea-5389-4863-87c0-cfa9faf06753%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwyW%3D3_E07cMHgo0wfn3KzBSDvL61LwrsffOi4wb6S_feQ%40mail.gmail.com.


[dspace-tech] GeoLite Database File Connot be downloaded

2020-01-16 Thread Ayuka Phanuel
I am running ant fresh_install and I am unable to download geolite database
file.
Am getting the below error. I am also unable to download the file manually.
Are the geolite services down or there is something else I need to do?

 [echo] Downloading:
http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.tar.gz
  [get] Getting:
http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.tar.gz
  [get] To: /var/www/html/dspace/config/GeoLite2-City.tar.gz
  [get] Error getting
http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.tar.gz to
/var/www/html/dspace/config/GeoLite2-City.tar.gz
 [echo]
 [echo]

 [echo] WARNING : FAILED TO DOWNLOAD GEOLITE DATABASE FILE
 [echo]   (Used for DSpace Solr Usage Statistics)
 [echo]
 [echo] Underlying Error: java.net.UnknownHostException:
geolite.maxmind.com
 [echo]
 [echo] In order to use DSpace Solr Usage Statistics, you will need to
 [echo] manually re-run:
 [echo]
 [echo] ant update_geolite
 [echo]
 [echo] OR
 [echo]
 [echo] You may manually install this file by following these steps:
 [echo] (1) Download the latest database archive from
http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.tar.gz
 [echo] (2) Unpack it.'
 [echo] (3) Copy the file 'GeoLite2-City.mmdb' to
'${usage-statistics.dbfile}'.


*Kind Regards, *
*Phanuel Ayuka.*
*Systems Developer - **Android | Django | Java EE | ODK Aggregate | PHP*

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwz-SHb%2BdMu%2BmtgZ9NXnv5eWheAEk3EiaO7xDtX9Y4cVrA%40mail.gmail.com.


Re: [dspace-tech] Re: Handle.Net Server Set up

2019-12-13 Thread Ayuka Phanuel
Thanks Alan,
With the above command I was able to identify the processes  using the two
ports and killed them. Handle server is now running fine.

*Kind Regards, *
*Phanuel Ayuka.*
*Systems Developer - **Android | Django | Java EE | ODK Aggregate | PHP*


On Thu, Dec 12, 2019 at 1:38 PM Alan Orth  wrote:

> Dear Phanuel,
>
> "Address already in use" means that some program is already listening on
> the IP:port that your handle service is configured for. Could be TCP ports
> 2641 or 8000, or UDP port 2641. Check on Linux with:
>
> $ sudo lsof -i -n -P | grep -E '(2641|8000)'
>
> Regards,
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwyOaSNqZk1TzbvQXbPJFLwOQvjd%3D0ZTh%2BpxnSgpQBqXTw%40mail.gmail.com.


[dspace-tech] Re: Handle.Net Server Set up

2019-12-09 Thread Ayuka Phanuel
Anyone with a solution to my problem?

*Kind Regards, *
*Phanuel Ayuka.*



On Fri, Dec 6, 2019 at 7:52 PM Ayuka Phanuel  wrote:

> Our handle server has been working fine then stop after we changed the
> database name.
> We have reconfigured the handle server but it can not start. I am getting
> the error below:
>
>
>
>
>
>
> *Shutting down..."2019/12/06 03:08:12 WAT" 100 class
> net.handle.server.HdlUdpInterface: Error setting up server socket:
> java.net.BindException: Address already in use (Bind failed)"2019/12/06
> 03:08:12 WAT" 100 class net.handle.server.HdlUdpInterface: Error setting up
> server socket: java.net.BindException: Address already in use (Bind
> failed)"2019/12/06 03:08:12 WAT" 100 class
> net.handle.server.HdlTcpInterface: Error setting up server socket:
> java.net.BindException: Address already in use (Bind failed)"2019/12/06
> 03:08:12 WAT" 100 class net.handle.server.HdlTcpInterface: Error setting up
> server socket: java.net.BindException: Address already in use (Bind
> failed)"2019/12/06 03:08:12 WAT" 100 class
> net.handle.server.HdlHttpInterface: Error setting up server socket:
> java.net.BindException: Address already in use (Bind failed)*
>
> Kindly assist.
> *Kind Regards, *
> *Phanuel Ayuka.*
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwze-5ALxm10wggE62PSqZQJFCSX3s2DfExNcknrF6L_dA%40mail.gmail.com.


[dspace-tech] Handle.Net Server Set up

2019-12-06 Thread Ayuka Phanuel
Our handle server has been working fine then stop after we changed the
database name.
We have reconfigured the handle server but it can not start. I am getting
the error below:






*Shutting down..."2019/12/06 03:08:12 WAT" 100 class
net.handle.server.HdlUdpInterface: Error setting up server socket:
java.net.BindException: Address already in use (Bind failed)"2019/12/06
03:08:12 WAT" 100 class net.handle.server.HdlUdpInterface: Error setting up
server socket: java.net.BindException: Address already in use (Bind
failed)"2019/12/06 03:08:12 WAT" 100 class
net.handle.server.HdlTcpInterface: Error setting up server socket:
java.net.BindException: Address already in use (Bind failed)"2019/12/06
03:08:12 WAT" 100 class net.handle.server.HdlTcpInterface: Error setting up
server socket: java.net.BindException: Address already in use (Bind
failed)"2019/12/06 03:08:12 WAT" 100 class
net.handle.server.HdlHttpInterface: Error setting up server socket:
java.net.BindException: Address already in use (Bind failed)*

Kindly assist.
*Kind Regards, *
*Phanuel Ayuka.*

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwzPsbPhg6YwHUUJFsOzbm%3DEK3vE2oU4So0yUOh1%2B900qw%40mail.gmail.com.


Re: [dspace-tech] Database connectivity Issue

2019-06-17 Thread Ayuka Phanuel
Confirm your database credentials (name, url, password, username) added to
your local.cfg or dspace.cfg



On Mon, Jun 17, 2019 at 4:21 PM Keith Jones  wrote:

> Hi All,
>
> I'm trying to move an installation of Dspace 5.3 to a new Centos 7
> server. I've installed all the software required and have everything
> running. I'm able to compile the Dspace software, which goes without a
> problem. I test the database connection and it works fine. When I
> deploy the xmlui into the webapps area of Tomcat, I'm getting the
> following error:
>
> SEVERE: Exception sending context destroyed event to listener instance
> of class org.dspace.app.util.DS
> paceContextListener
> java.lang.IllegalStateException: The connection attempt failed.
> at
> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:655)
> at
> org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:629)
> at org.dspace.core.Context.init(Context.java:121)
> at org.dspace.core.Context.(Context.java:95)
> at
> org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpaceWebapp.java:97)
> at
> org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpaceContextListener.java:146)
> at
> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5165)
> at
> org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5829)
> at
> org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
> at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260)
> at
> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.postgresql.util.PSQLException: The connection attempt
> failed.
> at
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:
> 152)
> at
> org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)
> at
> org.postgresql.jdbc2.AbstractJdbc2Connection.(AbstractJdbc2Connection.java:125)
> at
> org.postgresql.jdbc3.AbstractJdbc3Connection.(AbstractJdbc3Connection.java:30)
> at
> org.postgresql.jdbc3g.AbstractJdbc3gConnection.(AbstractJdbc3gConnection.java:22)
> at
> org.postgresql.jdbc4.AbstractJdbc4Connection.(AbstractJdbc4Connection.java:32)
> at
> org.postgresql.jdbc4.Jdbc4Connection.(Jdbc4Connection.java:24)
> at org.postgresql.Driver.makeConnection(Driver.java:393)
> at org.postgresql.Driver.connect(Driver.java:267)
> at java.sql.DriverManager.getConnection(DriverManager.java:664)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnec
> tionFactory.java:75)
> at
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java
> :582)
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> at
> org.dspace.storage.rdbms.DatabaseManager.initialize(DatabaseManager.java:1336)
> at
> org.dspace.storage.rdbms.DatabaseManager.getDataSource(DatabaseManager.java:650)
> ... 19 more
> Caused by: java.net.SocketException: Permission denied (connect failed)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net
> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net
> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net
> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at java.net.Socket.(Socket.java:434)
> at java.net.Socket.(Socket.java:211)
> at org.postgresql.core.PGStream.(PGStream.java:62)
> at
> org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryIm

Re: [dspace-tech] full item view mirage 2

2019-06-13 Thread Ayuka Phanuel
I also had the same issue with our view full metadata page in Mirage 2
DSpace version 6.3. The metadata names is always be shown as local.
instead of  even after I added the name to the messages.xml
I have not resolved this yet.






On Thu, Jun 13, 2019 at 9:45 PM Massimiliano CILURZO 
wrote:

> Hi Michael,
>   There is somthing very strange with the same messages.xml of my
> previous version 5.6 we can't see the correct label
> I tried the original messages.xml and messages_lang,xml of the mirage2
> theme and we have the same error.
> Another strange thing is that In the short view we see the correct label
> for Author.
> In dspace 6.3 we have to do a different configuation?
> Thanks
> best regards
> Massimiliano
>
>
>
>
>
> Il giorno giovedì 13 giugno 2019 15:03:11 UTC+2, Michael Plate ha scritto:
>>
>> Hi Massimiliano,
>>
>> Am 13.06.19 um 14:36 schrieb Massimiliano CILURZO:
>> > Hi Michael,
>> >
>> >I haven't touched the item-view.xls.
>> > I have modified the file messages_mylanguage.xml.
>> > But in english or in my language
>> > The system when I click on "show full item record" the system
>> visualize:
>> > dc.contributor.author
>> >
>> > dc.date.accessioned
>> > dc.date.available
>> >
>> > etc.
>> >
>> >
>> > I'd like to show "Author" and not dc.contributor.author as in my
>> > previous dspace server 5.6.
>>
>> and you have double checked the correctness (well formed) of the
>> message*xml file ?
>> Sorry if I insist on that, we had strange errors, too.
>> Did you try the original message-files from DSpace again, just to narrow
>> down the problem ?
>>
>> CU
>>
>> Michael
>>
>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/8d6094f6-14a3-4a85-969e-70939803a559%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwy103%2BEwooj7tFDi8AFRJwfijNhyn5bCMV30QzCWOq%2BbQ%40mail.gmail.com.


Re: [dspace-tech] Use REST to make Item Private

2019-05-20 Thread Ayuka Phanuel
What does this accomplish?
I might not have understood you well or my question is not very clear.


*Kind Regards, *
*Phanuel Ayuka.*







On Mon, May 20, 2019 at 12:43 PM Michael Plate <
pl...@bibliothek.uni-kassel.de> wrote:

> Hi Ayuka,
>
> Am 20.05.19 um 10:57 schrieb Ayuka Phanuel:
> > I have approximately 4000 items i need to make private in the
> > repository, Is there a way I can do this using the REST API.
> > The *edit this item and make private* in the XMLUI seems to be not very
> > feasible with the number of items I have.
> […]
>
> login as admin and below "Access control" choose "Authorization".
> On the top of the page you will find the line
>
> "Advanced authorizations tool:  Click here to go to the item wildcard
> policy admin tool"
>
> Click on it, it should be sufficient.
> Remember items and bitstreams - you can set rights for both, but you
> have to run each independent from the other.
>
> On large numbers of items you have to be patient :) .
>
>
> Michael
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/707e1418-f267-1c6e-2fdf-38a51d133310%40bibliothek.uni-kassel.de
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwy4Mo%3DzGJCHLZRkTZ7XS0bb5favhGAXs-ApeoxC3g48Tg%40mail.gmail.com.


[dspace-tech] Use REST to make Item Private

2019-05-20 Thread Ayuka Phanuel
I have approximately 4000 items i need to make private in the repository,
Is there a way I can do this using the REST API.
The *edit this item and make private* in the XMLUI seems to be not very
feasible with the number of items I have.


*Kind Regards, *
*Phanuel Ayuka.*

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAOSLvwz6RdCsUm_EcV7yQ3CFVaMXN%3D%2BFAPGrL3jgaTvjQ17TPQ%40mail.gmail.com.


[dspace-tech] Making another author metadata

2019-04-10 Thread Ayuka Phanuel
I am working on dspace 6 and XMLUI. I have a requirement where we need to 
distinguish the main authors and contributing authors in a publication.
Can i just  I create a new metadata field same as dc.contibutor.author and 
name it as dc.contributor.otherauthors?

Will the field have the same functionalities like the author metadata as 
shown in the *person lookup*?

-- 
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: 2 queries about installing DSPACE 6

2019-04-08 Thread Ayuka Phanuel
Just run the mvn and ant commands without adding sudo.
e.g
mvn clean package
ant fresh_install

and not

sudo mvn clean package
sudo ant fresh_install







On Mon, Apr 8, 2019 at 12:54 PM Ashim Kapoor 
wrote:

>
>
> On Mon, 8 Apr 2019 at 12:28, Paul Münch 
> wrote:
>
>> Dear Ashim,
>>
>> the answer of your first question find you here:
>> https://wiki.duraspace.org/display/DSDOC6x/REST+API#RESTAPI-DisablingSSL
>>
>> To your second question: Maybe you run maven/ant once as root, so there
>> are some files which assign to the root user. If not you have to look into
>> the 'chmod' documentation. It has nothing to do with the DSpace
>> installation itself.
>>
>
> Dear Paul,
>
> Many thanks. I did run maven and ant as root. What user should I run it as
> ? Please let me know.
>
> Best regards,
> Ashim
>
>
>
>
>> Kind regards,
>>
>> Paul Münch
>>
>>
>>
>> Am 05.04.19 um 18:09 schrieb Ashim Kapoor:
>>
>> Dear all,
>>
>> Can someone please help me ?
>>
>> Thank you,
>> Ashim
>>
>> On Thu, 4 Apr 2019 at 16:52, Ashim Kapoor 
>> wrote:
>>
>>> Dear All,
>>>
>>> I am installing DSPACE 6 on Debian 9 in a virtual machine.
>>>
>>> I am accessing the virtual machine from my computer.
>>>
>>> Query 1 :
>>>
>>> The REST page located at :
>>>
>>> https://192.100.30.66:8080/rest
>>>
>>> responds with :-
>>>
>>> Secure Connection Failed
>>> An error occurred during a connection to 192.100.30.66:8080. SSL
>>> received a record that exceeded the maximum permissible length. Error code:
>>> SSL_ERROR_RX_RECORD_TOO_LONG
>>> The page you are trying to view cannot be shown because the
>>> authenticity of the received data could not be verified.
>>> Please contact the website owners to inform them of this problem.
>>>
>>> How can I fix this problem?
>>>
>>> 2. My second query is :
>>>
>>> I did (prior to running maven and ant ) :
>>> chmod g+s [dspace]
>>>
>>> (This command ensures that the newly created files will inherit the
>>> permissions of the parent folder.)
>>>
>>> Then I did this :-
>>> chown -R tomcat8:tomcat8 [dspace]
>>>
>>> Then I did mvn and ant and the folder had permissions root and tomcat8
>>> in place of tomcat8 and tomcat8
>>> I still had to do chown -R tomcat8:tomcat8 [dspace] to make jspui work.
>>> Why is this ? It should have inherited the permissions. Can someone
>>> please explain ?
>>>
>>> Many thanks,
>>> Ashim
>>>
>>>
>>> --
>> 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.
>>
> --
> 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.
>

-- 
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: [Dspace-tech] Can't create administrator account after successful install of DSpace 5 RC 3

2019-04-05 Thread Ayuka Phanuel


The database clean command is disabled by default in dspace 6.x. Enable it 
first before running the command. And remember to set set is back to true 
on production which is the default.
>
>

-- 
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.