Hi,
On our dspace 1.7.2 production instance I made a small change in the dstat.cfg
file. Have done this several times in the
past in 1.6.2 dspace instances without any problem. Following is the change:
# DSpace information
# the year and month to start creating reports from
# - year as four
Gud day, I have installed dspace on my system and its working fine but I
have been trying to connect it from other local computer using wireless
router, and also with cross-over cable as an intranet but the othe system
are not connecting even when i use the ip address in edited in dspace.cfg
thats
---
Akeredolu Joshua wants to stay in better touch using some of Google's
coolest new
products.
If you already have Gmail or Google Talk, visit:
http://mail.google.com/mail/b-6778ac8521-9c0324b4b0-ckG-8GLO-nSTmEqMANfclaGqfxY
Hi Bill,
As Tim says, the METS package appears to have its metadata coded as DIM.
DSpace 1.5.2 didn't have a crosswalk to ingest DIM. This was added in
either 1.6 or 1.7. You need to either recreate your package to use a
format that DSpace 1.5 can understand (Mods or EPDCX), or copy the DIM
Hello,
In order to figure out what the real underlying error is, you'll have
to look at the DSpace Log files.
Please see the How to Troubleshoot an Error page for information
about finding the error in the log files:
https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error
Once you
Thank you for your answer Tim. I isolated the output generated on the
dspace.log file. It has a few warnings and two errors (I'm not sure how
critical they are).
Any pointers on where to look would be great.
--full command output on the console as follows
dspace@:/dspace/teste_exportacao$
I need some advice on the best (easiest, preferred) lightweight method for
exporting crosswalked metadata and bitstreams. I've read the crosswalk
configuration docs at
http://www.dspace.org/1_7_1Documentation/Configuration.html#Configuration-CrosswalkandPackagerPluginSettings
and the sysadmin
Hi Jason,
I'm not sure I fully follow your use case, but a few things you may wish
to look at (if you haven't already):
* If you are looking at exporting METS + bitstreams, have you taken a
look at the AIP Backup Restore feature (which generates AIPs that
are just zipped up METS files +
Hi people
Is there a way to enhace the discovery rank for documents that have fulltext?
I wish to present metadata's obtained results first than fulltext ones.
Thanks regards
German
--
Doing More with Less: The Next
On 15/09/2011, at 10:04 PM, Akeredolu Joshua wrote:
Gud day, I have installed dspace on my system and its working fine but I have
been trying to connect it from other local computer using wireless router,
and also with cross-over cable as an intranet but the othe system are not
connecting
This is a good one, what you want is to add filters to the query that will
attach wieght to the full text index to reduce its relevancy. To so this,
you will want to adjust the discovery solr schema to alter the relevancy in
the request handler.
I don't have specifics on those settings. It
I can't find any pattern in terms that I try with the REST API content
searching that cause it to return results versus this error:
The server encountered an internal error (Failure processing entity request
(/search.xml): null) that prevented it from fulfilling this request.
Does anyone know
Jason,
The AIP and default SWORD Packaging are biased towards METS, you'll want to
write your own packager to support the NLM Manifest format. To show you a
similar approach, here is the iMSCP IMLS packager used by MIT to ingest and
disseminate IMSCP Packages of OCW courses.
13 matches
Mail list logo
