Yes, it does make sense. It also means I must have something misconfigured
because the only way I can
currently access the site is if I explicitly specify http and port 8080 -
http://dspace36a.library.uaf.edu:8080/
On Friday, October 26, 2018 at 12:37:42 PM UTC-8, Tim Donohue wrote:
>
> Hi Walt
Hi Walter,
No worries, we've all been newbies at some point :)
Port 8080 is Tomcat. It should not be defined in Apache configuration.
Think of it this way, when you use Apache in front of Tomcat... your Tomcat
ports do *not* need to be publicly accessible. They are just internal ports
(only acces
Good to know. That should simplify things.
Now for the embarrassing newb questions. I'm still not clear how my httpd
secures port 8080
(which everything is going through now) since a URL that includes port 8080
isn't handled by
the port 443 virtual host configuration. And how does port 8009 (AJP
Hi Diego,
At this time "Browse by..." options (webui.browse.index.* configs) are not
customizable per Collection. I'm not aware of anyone who has done that,
but hopefully someone will speak up if they have found a way to achieve
this within DSpace (as it'd likely require custom code, etc.)
- Tim
>
> Hi. In dspace.cfg file there is a section named ## Browse
> Configuration ## where default browse indexes are defined. So, there I
> have:
>
> webui.browse.index.1 = title:item:title
> webui.browse.index.2 = subject:metadata:dc.subject.*:text
> webui.browse.index.3 = area:metadata:ar
Hi Walter,
The dspace.cfg settings (any that use a URL) do not *require* a port
number. The port number only needs to be specified if it's a non-standard
port (e.g. 8080). So, if you are using port 80 or 443, those can be left
off of any configuration as long as you appropriately use http:// or
Estimados
Tengo una instalación de Dspace 6.2 en Debian.
Como se trata de una instalación para desarrollo, importe los registros
mediante un pg_dump/pgrestore desde una instalación de producción que
funciona ok.
El problema que tengo es que me muestra los archivos de algunos items si y
de otros
Hi Christoph,
That is odd. Are there any additional error messages in your Tomcat logs?
Usually errors like the "org.dspace.core.exception.
DatabaseSchemaValidationException: The schema validator returned: Error
activating Bean Validation integration" will have a "Caused By:" message
which gives y
Hello,
DSpace does not have modules for comments, share/like or evaluation
available at this time. It's possible you could purchase some of them
through third-party service providers (if any have such modules available
for purchase). https://duraspace.org/dspace/resources/service-providers/
- Ti
Hi Tomas,
I suspect your "handle.canonical.prefix" configuration may be
misconfigured. This is the configuration DSpace uses to determine what URL
to store in your "dc.identifier.uri" field (which is that "URI" field you
see on the Item pages). Normally it is set to "[your-url]/handle/", for
exam
Hi, I have strange problem my dspace url is: myuniversity.com, but in
submitted or aprooved item window I gen generated url like this:
http://localhost:8080//xmlui/handle/123456789/89
how can I fix this?
thanks for help!
--
All messages to this mailing list should adhere to the DuraSpace C
11 matches
Mail list logo
