you can check the subject filter field name
maybe dc.subject.lcsh or another
so you must change the dc.subject_filter to dc.subject.lcsh_filter
On Tue, May 3, 2011 at 4:54 AM, Nemiz, Elvi S. wrote:
> Dear Kim,
>
> I followed your instructions in your blog
> http://kim-shepherd.blogspot.com/2010/
Dear Sir,
Very good morning. I want to change the table header of simple
search page for different collection. Now it always shows Author,
Title, Issue date. I want to change this according to search on
different collection. Example for student collection it would be Name,
ID and issue da
Andrea:
Ahhh...I didn't think about the metadata export import! Great Idea! I still
think someone needs to fix the code, though, since it works in 1.6.2
For all code busters out there, here is the error:
2011-05-02 16:25:33,944 WARN org.dspace.content.DCDate @ Mangled date: April,
1994 ..fa
Thank you, Hardy.
Yes, I thought that it would be a SQL fix. I was hoping for a "non-techy" for
my colleagues who don't do database management. Oh, well.
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CULIT)
501 Olin Library
Cornell University
Itha
Dear Kim,
I followed your instructions in your blog
http://kim-shepherd.blogspot.com/2010/11/discovering-discovery-dspace-solr-tips.htmlbut
I want to apply it in dc.type. I want to configure all entries in
dc.type as a facet but I can't make this facet appear.
I have added the following in my sche
Hi, Tim, we haven't run into any other Oracle issues in our on-going
testing of 1.7.1. We're running a version of 1.7.1 that's been patched
with the patch I submitted for DS-841 (which I feel is pretty hacky, just
rolling back a change, but writing something better that incorporates the
change in a
Bram,
Unfortunately, we had no luck with the following. After adding the fields to
the schema.xml and deleting the index and reindexing, we found that they still
were appearing in the dropdown suggestions. I've included what we added below,
and the options around it as well, to show the general
Tim,
There is absolutely no requirement to have an Oracle license for a
testathon. The Oracle XE database is easy to install, works exactly the same
as the full licensed copy, and we'll get nowhere near the limits in data
sizes for the purposes of a testathon.
I'm quite happy to assist with imple
Hi George,
On 03/05/11 08:41, George Stanley Kozak wrote:
> In DSpace 1.6.2, these records display properly except that the Date
> display is something like “-1-Uns- -1”. No problem, I can go in and
> fix them.
>
> In Dspace 1.7.1 (using the JSPUI interface), these types of records
> do not dis
Hi Hardy & Richard,
I'll readily admit that our Oracle support has been more difficult
recently. The primary reason for this is that the Committer who was
leading DSpace's Oracle support has moved on to a different role and no
longer works with DSpace. So, at this point in time, we have no (zer
Hi, George, I've run into some odd display problems that related to
metadata that was wrong in unplanned-for ways, such as an incomplete or
null URI field (due to quota issues with our database). I ended up
resolving those issues by working with the Oracle tables directly, using
SQL Developer on my
Hi, Everyone:
Last Friday I wrote about a "bug" that I found in DSpace 1.7.1, and I haven't
heard back from anyone about this. So, I am thinking that what I wrote wasn't
clear enough, and, therefore, I am resubmitting my email with some additional
information.
I have some records that someon
Quick FYI:
Bugs/patches for the REST API can actually be submitted directly to our
JIRA at:
https://jira.duraspace.org/browse/DS
Just be sure that when you submit the bug/patch, you select the
"Component" as "REST API (experimental)".
- Tim
On 5/2/2011 1:13 PM, Peter Dietz wrote:
> Hi All,
>
Hi All,
I was looking at the DSpace REST API module today, and I too had errors with
getting null when viewing something like:
http://localhost:8080/restapi/communities/213.xml
*message* *Failure processing entity request (/communities/213.xml): null*
*description* *The server encountered an int
Hi, in my previous message, I made a misleading and incorrect reference to
the list which should properly be referred to as the changelog list; for
posterity's sake, here's a link to the correct mail list:
https://lists.sourceforge.net/lists/listinfo/dspace-changelog
I'm adding myself now, follo
Hi, Richard, I think what needs to happen is someone from our community of
Oracle installations needs to commit an Oracle-backed installation to the
next Testathon, to catch items like this. I am also going to try to do
more testing along the way. I think what we need to do as a community is
to be
Dear DSpace Community,
The DSpace User Group will take place in Austin, Texas, USA , June 10, 2011
(afternoon) and June 11, 2011 (morning).
While the schedule is not yet set, you can view accepted proposals on the OR11
conference website:
https://conferences.tdl.org/or/OR2011/OR2011main/sche
We have encountered the problem reported previously by Peter Dietz:
http://dspace.2283337.n4.nabble.com/DuraSpace-JIRA-Created-DS-841-Illega
lArgumentException-No-such-column-rnum-error-in-DSpace-1-7-x-XML-td33815
04.html
('IllegalArgumentException: No such column rnum' error in DSpace 1.7.x
Hello all,
I was trying to upgrade my DSpace from 1.3.2 version to DSpace 1.7.0.
thanks for the help from u guys fro the initial start...
Now i'm stuck somewhere else...that is changing database schema from 1.3 to
1.4 was sucessful but 1.4 to 1.5 give me errors:
psql -f database_schema_13-14.sql
19 matches
Mail list logo
