[dspace-tech] Re: Compiling DSpace 6 with Mirage2 theme does not generate CSS files

[Ari]

Hello Pedro,
upgrading maven was enough for me. I'm quite certain that I didn't do 
anything else. Did you get any errors on compile?

Ari

On Thursday, 3 November 2016 17:40:17 UTC+2, Pedro Amorim wrote:
>
> Hello Ari. Im having the exact same problem. So I installed maven 3.3.9 
> and rebuilt DSpace with mvn package.
> However, now XMLUI only shows the error:
> FileNotFoundException: dspace/webapps/xmlui/themes/Mirage2/sitemap.xmap
>
> Did you do any other additional procedures ?
>
> Thanks,
> Pedro Amorim
>
>

-- 
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] Embargo settings

[Fitchett, Deborah]

Kia ora koutou,

We’re starting to play with the embargo functionality, in v5.6 XMLUI (Mirage) – 
but to complicate matters most of our items are submitted from Symplectic 
Elements. It may turn out that we have to do a lot manually but first I want to 
test what we can do automatically and I’m running into some Unexpected 
Behaviour.

Our dspace.cfg embargo settings are:

 Embargo Settings 
# DC metadata field to hold the user-supplied embargo terms
embargo.field.terms = lu.embargo.ends

# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = lu.embargo.enddate

# string in terms field to indicate indefinite embargo
embargo.terms.open = forever
embargo.terms.days = 3 months:91,6 months:182,9 months:274,12 months:365,1 
year:365,15 months:456,18 months:548,21 months:639,24 months:730

# implementation of embargo setter plugin - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoSetter = 
org.dspace.embargo.DefaultEmbargoSetter

# implementation of embargo lifter plugin - - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoLifter = 
org.dspace.embargo.DefaultEmbargoLifter


(For submitting through the web interface I’ve enabled the submission step to 
let users add an embargo at the bitstream level; I’ve left out the step to add 
an embargo at the item level because this doesn’t suit our workflow. I don’t 
*think* this is relevant here but it might be...)

When I submit an item via Elements, the term “6 months” is put into the field 
lu.embargo.ends (I’ve verified this by checking directly in the database).
When I check the metadata when it’s in workflow, I don’t see any end-date 
calculated – so I assume that it’ll calculate this on committal to the archive.
But when I click ‘commit to archive’ I get the error: “Embargo lift date must 
be in the future, but this is in the past: 6”

So it appears to be attempting to interpret the term “6 months” as a date by 
throwing out the alpha characters and complaining that 6 < 2016-11-04  - 
instead of converting “6 months” -> 182 days and adding that to the current 
date as I thought it was meant to do.

Am I missing something; or is this a bug; or is it a bad interaction with 
Elements?


Kā mihi maioha,

Deborah Fitchett
Senior Advisor, Digital Access
Library, Teaching and Learning

p +64 3 423 0358
e deborah.fitch...@lincoln.ac.nz | w 
ltl.lincoln.ac.nz

Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's specialist land-based university



P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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: help with large file uploading configuration options for JSPUI

[Hardy Pottinger]

bug: https://jira.duraspace.org/browse/DS-3375

On Thu, Nov 3, 2016 at 4:40 PM, Hardy Pottinger 
wrote:

> An update: I have discovered that the upload actually succeeds, the UI
> just doesn't reflect success (a yellow exclamation mark appears). I've
> tested the same upload on demo.dspace.org, and it also seems to fail, but
> the file is there.
>
> So... I think this is a bug. I'll open a Jira ticket for it shortly.
>
> --Hardy
>
> On Thu, Nov 3, 2016 at 3:08 PM, Hardy Pottinger  > wrote:
>
>> Hi, remember this discussion back in 2012 re enabling large file uploads?
>>
>> http://dspace.2283337.n4.nabble.com/Ingesting-large-data-
>> set-td4657204.html
>>
>> I am currently setting up a data repository, and we'd prefer to use the
>> JSPUI. The tips in the thread I just linked refer to some XMLUI-specific
>> settings, and, I'm wondering if any JSPUI user on this list might have a
>> similar list of things to check for enabling large file uploads?
>>
>> Currently, on our test repository, I can confirm a 13MB upload works
>> fine, but a 76MB upload fails. I know, that's hardly "large." I'm somewhat
>> confused by the how the upload fails-- the progress bar goes to nearly full
>> on the browser, and then fails. The only error message in the logs is an
>> NPE during the attempt to email an error report:
>>
>> https://gist.github.com/hardyoyo/5cabefb4eb774c680ebf7bda7f1f0f9c
>>
>> Any hints?
>>
>> --Hardy
>>
>
>

-- 
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: help with large file uploading configuration options for JSPUI

[Hardy Pottinger]

An update: I have discovered that the upload actually succeeds, the UI just
doesn't reflect success (a yellow exclamation mark appears). I've tested
the same upload on demo.dspace.org, and it also seems to fail, but the file
is there.

So... I think this is a bug. I'll open a Jira ticket for it shortly.

--Hardy

On Thu, Nov 3, 2016 at 3:08 PM, Hardy Pottinger 
wrote:

> Hi, remember this discussion back in 2012 re enabling large file uploads?
>
> http://dspace.2283337.n4.nabble.com/Ingesting-large-
> data-set-td4657204.html
>
> I am currently setting up a data repository, and we'd prefer to use the
> JSPUI. The tips in the thread I just linked refer to some XMLUI-specific
> settings, and, I'm wondering if any JSPUI user on this list might have a
> similar list of things to check for enabling large file uploads?
>
> Currently, on our test repository, I can confirm a 13MB upload works fine,
> but a 76MB upload fails. I know, that's hardly "large." I'm somewhat
> confused by the how the upload fails-- the progress bar goes to nearly full
> on the browser, and then fails. The only error message in the logs is an
> NPE during the attempt to email an error report:
>
> https://gist.github.com/hardyoyo/5cabefb4eb774c680ebf7bda7f1f0f9c
>
> Any hints?
>
> --Hardy
>

-- 
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] help with large file uploading configuration options for JSPUI

[Monika Mevenkamp]

We deal with big files as follows

submitter enters metadata and uploads README.txt file 
puts the BIG file(s) somewhere so I can copy to DSPACE server 
I approve the submission and use  itemupdate to add the BIG file 

I have a directory with the AIP files which I tweak each time: 
1) change the contents file 
2) edit the dublin_core.xml to refer to right URL 
3) run: /dspace/bin/dspace itemupdate -e moni...@princeton.edu -v -A -s import

not ideal - but works fine for infrequent uploads 

Monika 

 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



> On Nov 3, 2016, at 4:08 PM, Hardy Pottinger  wrote:
> 
> Hi, remember this discussion back in 2012 re enabling large file uploads?
> 
> http://dspace.2283337.n4.nabble.com/Ingesting-large-data-set-td4657204.html 
> 
> 
> I am currently setting up a data repository, and we'd prefer to use the 
> JSPUI. The tips in the thread I just linked refer to some XMLUI-specific 
> settings, and, I'm wondering if any JSPUI user on this list might have a 
> similar list of things to check for enabling large file uploads?
> 
> Currently, on our test repository, I can confirm a 13MB upload works fine, 
> but a 76MB upload fails. I know, that's hardly "large." I'm somewhat confused 
> by the how the upload fails-- the progress bar goes to nearly full on the 
> browser, and then fails. The only error message in the logs is an NPE during 
> the attempt to email an error report:
> 
> https://gist.github.com/hardyoyo/5cabefb4eb774c680ebf7bda7f1f0f9c 
> 
> 
> Any hints?
> 
> --Hardy
> 
> -- 
> 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 
> .

-- 
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] help with large file uploading configuration options for JSPUI

[Hardy Pottinger]

Hi, remember this discussion back in 2012 re enabling large file uploads?

http://dspace.2283337.n4.nabble.com/Ingesting-large-data-set-td4657204.html

I am currently setting up a data repository, and we'd prefer to use the
JSPUI. The tips in the thread I just linked refer to some XMLUI-specific
settings, and, I'm wondering if any JSPUI user on this list might have a
similar list of things to check for enabling large file uploads?

Currently, on our test repository, I can confirm a 13MB upload works fine,
but a 76MB upload fails. I know, that's hardly "large." I'm somewhat
confused by the how the upload fails-- the progress bar goes to nearly full
on the browser, and then fails. The only error message in the logs is an
NPE during the attempt to email an error report:

https://gist.github.com/hardyoyo/5cabefb4eb774c680ebf7bda7f1f0f9c

Any hints?

--Hardy

-- 
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] Running vagrant-dspace ?

[Tom Hutchinson]

Hi Charles,

Vagrant-dspace worked for me a couple weeks ago.

However I couldn't get local.yaml to work. I wasn't able to use
sync_src_to_host or set the git options. I haven't had time to
re-visit the issue since.

I tried things again just now on a different computer than before. I
couldn't get it to work (vagrant up failed) until I set up my SSH key
with github. This was without using local.yaml (will try that later).

I added my key to ssh agent [1] and then tested the connection [2]. It
remembered the github fingerprint (added an entry to
~/.ssh/known_hosts).

Certainly possible that's a red herring (especially considering I
don't really know vagrant).

Please report back if you figure anything out.

Tom

[0] https://help.github.com/categories/ssh/
[1a] eval "$(ssh-agent -s)")
[1b] ssh-add ~/.ssh/id_rsa
[2] ssh -T g...@github.com

On Tue, Nov 1, 2016 at 9:35 AM,   wrote:
> I'm trying to evaluate DSpace as a potential replacement for our current
> institutional repository.
>
> Has anyone tried to run the Vagrant box from this project
> https://github.com/DSpace/vagrant-dspace lately ?
>
> It just fires up and ends in a timeout because it cannot connect via SSH.
> I'm using Vagrant 1.8.6, and have other projects running flawlessly.
>
> I suspect that vagrant-dspace is broken since DSpace 6 was released ... but
> unfortunately I'm not in the capacity to fix it, as I get no error message
> and cannot connect to the box.
>
> Any help would be greatly appreciated.
>
> ++
>
> --
> 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.

-- 
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] missing email address in dc.provenance

[Hannah]

I am seeing this same issue with Dspace 5.4, since I enabled the 
XmlWorkflow. Is there any way to ensure that email addresses are included 
on every submission?

Thanks,

Hannah

On Friday, April 22, 2016 at 10:24:38 AM UTC-7, Bill T wrote:
>
> Thanks Andrea!  By 'user error', I meant me ;)
>
> Yes, I see the email address is being generated here, but recordStart is 
> only called in the case where there is a workflow, correct?
>
> In XmlWorkflowItem.start() we have:
>
> if(firstStep == null) {
>   archive(context,wfi);  // which calls InstallItem.installItem() where 
> the 'Made available' provenance is generated.
> }
> else {
>   activateFirstStep(context,wf,firstStep,wfi);
> // which calls activateFirstStep which calls recordStart() where the 
> 'Submitted by' provenance is generated.
> }
>
> What I see happening, is that when there is one (or more) workflow steps 
> for a collection, these records include the 'Submitted by' provenance 
> value, but when records are submitted without a workflow, only the 'Made 
> available' value is added...
>
> Bill
>
> On Thursday, April 21, 2016 at 12:40:17 AM UTC-5, Andrea Schweer wrote:
>>
>> Hi Bill, 
>>
>> On 21/04/16 05:48, Bill T wrote: 
>> > In DSpace5.5/xmlui, with XmlWorkflow enabled, the submitter's email 
>> > address is no longer included in the auto-generated dc.provenance 
>> > metadata field. 
>> > 
>> > Bug or user error? 
>>
>> I can't see how this would be user error, if you mean user=end user. It 
>> could simply be that the XML workflow code is different from the 
>> traditional workflow in that regard. However -- it looks like the code 
>> still includes the e-mail address, see here: 
>>
>> XML workflow: 
>>
>> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace-api/src/main/java/org/dspace/xmlworkflow/XmlWorkflowManager.java#L826
>>  
>>
>> Traditional workflow: 
>>
>> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace-api/src/main/java/org/dspace/workflow/WorkflowManager.java#L1154
>>  
>>
>> Or do you mean a different provenance message? The one generated by the 
>> XML workflow code I linked to should include "workflow start=". 
>>
>> cheers, 
>> Andrea 
>>
>> -- 
>> Dr Andrea Schweer 
>> Lead Software Developer, ITS Information Systems 
>> The University of Waikato, Hamilton, New Zealand 
>> +64-7-837 9120 
>>
>>

-- 
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: Compiling DSpace 6 with Mirage2 theme does not generate CSS files

[Pedro Amorim]

Hello Ari. Im having the exact same problem. So I installed maven 3.3.9 and 
rebuilt DSpace with mvn package.
However, now XMLUI only shows the error:
FileNotFoundException: dspace/webapps/xmlui/themes/Mirage2/sitemap.xmap

Did you do any other additional procedures ?

Thanks,
Pedro Amorim

-- 
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] enable https in tomcat dspace public access

[helix84]

Hi Binta,

apart from what Tom said, which is all good advice, I'd like to add
that terminating SSL at Tomcat like you're trying to do is a perfectly
fine option (as long as you don't plan on using Shibboleth SP,
mod_rewrite or other Apache-specific modules).

There's a catch with SSL connector configuration, though. There are
three implementations in Apache:
* Http11AprProtocol - the one you tried to use - will work iff you're using APR
* Http11NioProtocol - will work iff you're not using APR
* Http11Protocol - will work iff you're not using APR

This is all described in the Tomcat documentation (the whole page is
relevant; this is the part on context configuration). Use Tomcat
documentation for your Tomcat version. This one is for Tomcat 7:

https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Edit_the_Tomcat_Configuration_File


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Thu, Nov 3, 2016 at 11:02 AM, Saidy Binta  wrote:
> Hi All,
>
>
>
> Please see configuration on tomcat but I cannot still access tomcat on
> https. Please direct me on the way forward.
>
>
>
>  SSLEnabled="true"
>
>maxThreads="150" scheme="https" secure="true" SSLEngine="on"
> clientAuth="false"
>
>SSLCertificateFile="X:/certs/star_mrc_gm.p7b"
> SSLCertificateKeyFile="X:/certs/star_mrc_gm.pem"
>
>sslProtocol="TLS"  />
>
>
>
>
>
> regards
>
> Binta
>
>
> 
>
> DISCLAIMER: This message is private and confidential. If you have received
> this message in error please notify us and remove it from your system. Any
> views and opinions expressed in this message are those of the individual
> sender and do not necessarily represent the views and opinions of MRC Unit
> The Gambia.
>
> ___
> This communication is confidential and may contain privileged information
> intended solely for the named recipient(s). It may not be used or disclosed
> except for the purpose for which it has been sent. If you are not the
> intended recipient, you must not copy, distribute, take any action or
> reliance on it. If you have received this communication in error, do not
> open any attachments but please notify the Help Desk by e-mailing
> h...@mrc.gm quoting the sender details, and then delete this message along
> with any attached files. E-mail messages are not secure and attachments
> could contain software viruses which may damage your computer system. Whilst
> every reasonable precaution has been taken to minimise this risk, The MRC
> Unit The Gambia cannot accept any liability for any damage sustained as a
> result of these factors. You are advised to carry out your own virus checks
> before opening any attachments. Unless expressly stated, opinions in this
> message are those of the e-mail author and not of the Medical Research
> Council Unit The Gambia.
> 
>
> --
> 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.

-- 
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] enable https in tomcat dspace public access

[Tom Hutchinson]

Hi Binta,

I think my setup is a bit different than yours. I'm using Apache in
front of Tomcat. My Apache is open to the world with SSL turned on.
Then it connects to Tomcat using AJP and mod_proxy. My Tomcat is not
directly accessible outside of the server.

Are you redirecting port 443 to 8443? Are you able to access the site
if you add :8443 to the address? (e.g.
https://not.myrealaddress.com:8443)

Another possibility is that you are running into firewall/port issues.
I had to open port 443 using iptables. I suggest trying to connect
from within the server. You can ssh in and use a text based web
browser such as links or lynx. Try accessing https://localhost:8443 If
that works, try accessing https://localhost (https defaults to port
443)

The good thing is that these tomcat setup issues aren't specific to
DSpace. I used the official DSpace documentation but also ran plenty
of searches about setting up tomcat/apache (unrelated to DSpace).

Regards,

Tom

On Thu, Nov 3, 2016 at 6:02 AM, Saidy Binta  wrote:
> Hi All,
>
>
>
> Please see configuration on tomcat but I cannot still access tomcat on
> https. Please direct me on the way forward.
>
>
>
>  SSLEnabled="true"
>
>maxThreads="150" scheme="https" secure="true" SSLEngine="on"
> clientAuth="false"
>
>SSLCertificateFile="X:/certs/star_mrc_gm.p7b"
> SSLCertificateKeyFile="X:/certs/star_mrc_gm.pem"
>
>sslProtocol="TLS"  />
>
>
>
>
>
> regards
>
> Binta
>
>
> 
>
> DISCLAIMER: This message is private and confidential. If you have received
> this message in error please notify us and remove it from your system. Any
> views and opinions expressed in this message are those of the individual
> sender and do not necessarily represent the views and opinions of MRC Unit
> The Gambia.
>
> ___
> This communication is confidential and may contain privileged information
> intended solely for the named recipient(s). It may not be used or disclosed
> except for the purpose for which it has been sent. If you are not the
> intended recipient, you must not copy, distribute, take any action or
> reliance on it. If you have received this communication in error, do not
> open any attachments but please notify the Help Desk by e-mailing
> h...@mrc.gm quoting the sender details, and then delete this message along
> with any attached files. E-mail messages are not secure and attachments
> could contain software viruses which may damage your computer system. Whilst
> every reasonable precaution has been taken to minimise this risk, The MRC
> Unit The Gambia cannot accept any liability for any damage sustained as a
> result of these factors. You are advised to carry out your own virus checks
> before opening any attachments. Unless expressly stated, opinions in this
> message are those of the e-mail author and not of the Medical Research
> Council Unit The Gambia.
> 
>
> --
> 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.

-- 
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] Modify home screen in XMLUI

[Tom Avino]

We are upgrading Dspace 3.3 JSPUI to 5.5 XMLUI.
Our system requires a disclaimer screen before showing the home screen.  In 
the JSPUI version, we just modified the home.jsp to include the disclaimer, 
then created a sitehome.jsp as the new home screen.
I need to basically do the same, but using XMLUI.  I am new to XMLUI, so 
any help would be appreciated.

Thank you,

*Tom Avino *

LITES II Application Developer | SAIC 

o: 757.864-8495 | thomas.w.av...@nasa.gov 

f:  757.864-6649 | thomas.av...@saic.com


-- 
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] enable https in tomcat dspace public access

[Saidy Binta]

Hi All,

Please see configuration on tomcat but I cannot still access tomcat on https. 
Please direct me on the way forward.




regards
Binta



DISCLAIMER: This message is private and confidential. If you have received this 
message in error please notify us and remove it from your system. Any views and 
opinions expressed in this message are those of the individual sender and do 
not necessarily represent the views and opinions of MRC Unit The Gambia.

___
This communication is confidential and may contain privileged information 
intended solely for the named recipient(s). It may not be used or disclosed 
except for the purpose for which it has been sent. If you are not the intended 
recipient, you must not copy, distribute, take any action or reliance on it. If 
you have received this communication in error, do not open any attachments but 
please notify the Help Desk by e-mailing h...@mrc.gm quoting the sender 
details, and then delete this message along with any attached files. E-mail 
messages are not secure and attachments could contain software viruses which 
may damage your computer system. Whilst every reasonable precaution has been 
taken to minimise this risk, The MRC Unit The Gambia cannot accept any 
liability for any damage sustained as a result of these factors. You are 
advised to carry out your own virus checks before opening any attachments. 
Unless expressly stated, opinions in this message are those of the e-mail 
author and not of the Medical Research Council Unit The Gambia.


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