Hi,
When I submit a new document, it shows in my submissions, it has the
status archived, but it does not show in the collection where it was
submited.
What am I doing wrong?
Also, the document has an handle of the time
http://hdl.handle.net/123456789/4 but I am not using handle.net and the
Dear Community Members,
We have converted messages.properties in Tamil Language. Request your
guidance on finding unicode code for Tamil and how to convert current
solution in bi-lingual solution.
Thanks,
Iyer
--
How do I enable the login as e-person button when managing e-persons?
It doesn't seem to be enabled in a new 4.2 install.
Chris Gray
Systems Analyst
519-888-4567, ext. 35764
cpg...@uwaterloo.ca
University of Waterloo
Hey everybody!
This is not a dspace specific question, but i hope someone can help me.
I'm implementing a Ruby sword client to submit itens to dspace using a
custom interface. I did some research and i found sword2ruby
library, but i'm trying to execute the example given on the project
git page
I've never used the SWORD protocol, but it should be pretty easy to avoid the
mimetype exception (for the SWORD V2 interface).
I'm assuming that atomserv+xml and atomsvc+xml are used by different
services to identify the same SWORD/XML format. From some quick testing, it
seems like this is the
I am experimenting with the Curation System. I have written a task to
crawl a collection/community and identify specific items that are exception
cases (restricted items, multiple bitstreams, non-standard bitstream type).
https://gist.github.com/terrywbrady/24f6ddf24d9026149aff
The process is
Thank you all guys for your time and your help.
I managed to solve the problem.
Basically the problem was with renaming the old versions of dsicovery.xml
to something like that discovery-old-16-Dec-14.xml, and What I noticed
that the old files was picked up instead of the updated file.
So When
Hi Bruno,
I'm not very familiar with swordv2, but the sword v1 error is coming from
dspace. Usually dspace expects a zipped package of some type (by default,
it expects the dspace mets format, though I think it can be configured to
accept SAF, look in the sword-server.cfg file in the dspace/config
Hi Terry:
I’m away from the office with limited network, but based on a quick look at the
code, I have a few suggestions.
You don’t indicate how you run this task, but I’m assuming that for the large
collections at least, you are not doing it in the admin UI but with the
command-line tool.
It
Hello,
I was wondering if anyone else has run into this issue. We made a small
customization our input-forms.xsl file for two collections. We uploaded
the file in our test environment and it worked great. The changes loaded
right away with no need for a restart. Then we adapted it for our
I am not familiar with the the initialization of that file, so this
recommendation is just a quick guess.
When I have run into situations like the one you describe, I presume it is
that the caching on my production server is more active than on my test
server.
If you are running XMLUI, try
Hi All,
We've rigged up DSpace 4.2 to accept METS (zip) packages via the Sword 2
API and am now looking at a couple of items. I thought that, in the first
instance, I'd see if the following are possible:
1. Is it possible to set the DSpace object's visibility via the METS
metadata?
For example,
12 matches
Mail list logo
