Hi Terry,
So resource_id and resource_type_id identify in the metadatavalue identity
the ePerson and Item? And what about the Bitstream?
Do you know if this Database schema is valid:
https://wiki.duraspace.org/display/DSDOC5x/Storage+Layer?preview=/45548226/68355659/dspace5.png
Best regards
The discovery configuration file contains a default configuration and a
home page configuration.
https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/discovery.xml#L43-L46
Check your discovery.xml file to see if your new facets are applied to both
configurations.
Terry
On Fri,
DSpace 5 implemented a "Metadata for All Objects" feature. Most metadata
fields are now in the metadatavalue table.
Here is the migration code for eperson:
Does someone have a list of the dspace 5.5 postgres schema?
What specific postgres database changes were made from 3.3 to 5.5?
Other tables seem wrong. metadatavalue no longer contains item_id
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical
When I query an item, the item seems to display properly. However, when I
look in the log file I see this error. I am also having issues with
e-persons throwing errors.
ERROR org.dspace.content.DSpaceObject @ Loading item - cannot find metadata
field -1 for resourceType=3 and resourceId=29
Hi Pantelis,
This bug was resolved *after* the DSpace 6 RC1 release, as noted by Mark
Wood. Here's the bug ticket and resolution:
https://jira.duraspace.org/browse/DS-3104
https://github.com/DSpace/DSpace/pull/1364
So, if you are still running RC1, then you are likely encountering this bug.
Although the problem was manually corrected after creating the log dir and
setting the respective value in log4j.properties, I am still getting the
following error related to solr logs:
log4j:ERROR setFile(null,true) call failed.
*java.io.FileNotFoundException: /log/solr.log (No such file or
This should have been corrected in
https://github.com/DSpace/DSpace/pull/1364. log.dir no longer exists in
the DSpace configuration; it is only defined in the log4j configuration.
If a property is not defined, no substitution is done.
--
You received this message because you are subscribed
Resolved it was an issue of failed installation of pgcrypto.
On Sunday, May 22, 2016 at 6:59:05 PM UTC+3, Pantelis Karamolegkos wrote:
>
> The above target fails with the following output:
>
> [java] 2016-05-22 18:56:33,108 INFO
> org.dspace.services.caching.CachingServiceImpl @ destroy()
>
Still it seems it is unable to grasp the value of log.dir parameter and
substitute in log4j.properties.
My way around this was to hardcode the value of log.dir in log4j.properties
in which I now have an entry like:
log.dir=/home/pkaramol/Workspace/dspace6/dspace-6.0-rc1-install-dir/log
And I
can use google sign-in for dspace cris 5 ?
thank you
--
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
Thank you very much again Luigi Andrea
After I set *parameter: -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true *
*It work*
On Monday, May 23, 2016 at 5:40:28 PM UTC+7, Pascarelli Luigi Andrea wrote:
>
> Dear,
>
> as reported in the documentation:
>
>
> * If you use Tomcat 7, recommended, then
I use "startup.bat" to run server where I can set parameter ?
Thank you
--
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
Thank you very much, Luigi Andrea
I use tomcat 9.0 and don't set *parameter:
-Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true*
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving
Thank you very much, Franziska.
All is working now :-)
El dilluns, 23 maig de 2016 11:49:50 UTC+2, Mariangels va escriure:
>
>
> Hello,
>
> I'm working with DSpace 5.5 and xmlui (Mirage theme)
> I have a problem:
>
> When I'm browsing through the communities, collections, etc. I can see
> this
Hi Mariangels,
the search term (here: "predictor") was found in the fulltext of the
item, so DSpace does not display the abstract but snippets of the full
text where the search term was found.
You can fix this by commenting out
I installed DSpace CRIS 5 to my computer for testing.
by follow installation at
https://wiki.duraspace.org/display/DSPACECRIS/Installation
after installed, I copy jspui, solr, xmlui to webapps folder in apache
tomcat then, run webserver
create admin and testing, I found some thing wrong
when I
17 matches
Mail list logo
