Articles Im hoping to store in DSpace, may contain multiple authors from
different faculties / institutions. We're hoping to maintain the
author-faculty connection within the metadata. In other words; one
reading the metadata the should be able to tell which author comes from
which institution.
We do have more than one handle server running on the same machine. Cant
rememebr the details of what we did but looking at the
handle-server/config.dct file I can see that we are using different ports
for the "server_type" = "server" entry in each installation.
Hope that is some help.
Cheers, Ro
We faced the same problem (for journal articles with multiple authors
with different affiliations), but did not find any good solution to it.
One crude solution I was thinking about was to add numbered metadata
fields, one for each author, e.g:
dc.contributor.author1 = Smith, John
dc.contributor.a
Hi,
I use a custom input forms with several elements.
During the process of submission all elements are displayed properly but the
dc.publisher somehow is not displayed.
The input form for publisher is the following :
dc
publisher
true
Publisher
Hi Hilas,
the dc.publisher is tied to the initial-question
- has this item been published before
Only if this is checked dc.publisher, dc.date.issued are displayed afaik.
cheers
Claudia
Hlias Stavrakis schrieb:
> Hi,
>
> I use a custom input forms with several elements.
> During the process
On our production DSpace server we're managing around 12,243 items, but
around 430,000 bitstreams. We've seen a lot of issues with the server's
stability and are wondering if it's related to this large number of
bitstreams being managed. Has anyone else experienced stability problems
as the num
Hi geneva:
Can you characterize the stability problems a bit more? Errors or
sluggish responses, etc
Thanks,
Richard
Quoting Geneva Henry <[EMAIL PROTECTED]>:
> On our production DSpace server we're managing around 12,243 items, but
> around 430,000 bitstreams. We've seen a lot of issues with
Sluggish response and the platform goes down rather frequently. We have
a test server and development server running, with the test server
configured the same as the production server except for the content
load. The test environment works just fine so that's why we're thinking
it's the number
1) Searching in Google sometimes show the bitstreams of an item from the
repositories. How one can restrict robots from indexing bitstreams? It
should only index the metadata.
2) Running [dspace]/bin/install-configs or [dspace]/bin/stat-* as
dspace-user shows '[dspace]/log/dspace.log (Permission d
I would add that I've learned *never* to use a form of the name
"dspace" for directories, users, databases, .war files, etc. If an
instance will present itself as "Foo" then I'd name the [DSpace]
directory "foo", the database "foo", and the database user "foo", the
webapp.s "foo.war" and "foo-oai.
Geneva,
since you don't have a lot of items, this cannot be related to the browse
index problems in version 1.4.2 and earlier. It's the first time I'm seeing
such an issue (about number of bitstreams) since I'm following the DSpace
community so I'm very curious about the reason.
Can you te
Extending dc in that way is not a very good idea IMO, and I think the
DC community would not find it a acceptable practice to produce such
an "ad hoc" re-qualification of author and affiliation.
For the time being until relationships can be drawn between metadata
fields in dspace. I would re
Conal,
This is a good example of a simple aspect, thank you for sharing with
everyone. I wanted to address a few points in Dorothea's email
On Feb 5, 2008, at 9:53 AM, Dorothea Salo wrote:
>> I agree on the separation of concerns, adding content to the page
>> should be a different task than
Dorothea,
The bit of code that decides this is the AuthenticateAction,
org.dspace.app.xmlui.aspect.eperson.AuthenticateAction. The act()
method builds a redirect URL, first it checks to see if there was an
interrupted request. If so then in redirects to that url otherwise it
defaults to t
> The bit of code that decides this is the AuthenticateAction,
> org.dspace.app.xmlui.aspect.eperson.AuthenticateAction. The act()
> method builds a redirect URL, first it checks to see if there was an
> interrupted request. If so then in redirects to that url otherwise it
> defaults to the home pa
Hi Sid,
this is very useful informations that should be shared will all the DSpace
community. Also, I don't have a very good knowledge of Manakin so, maybe other
people could be of help.
If you actually experiencing some database performance issue, it could explain
why your batch importi
Hi Grahan
the code at www.jobim.org/dspace-xmlui is about one year old.
I just mentioned it because the submission aspect was working fine
for UTF-8 accented characters.
browsing and searching is working too but I had a few modifications
that I am making now in dspace-1.5_xx
I have almost every
DSpace Community,
We have seen lots of progress lately to move us more towards the
DSpace 1.5 release but there is still more to do. The major road
blocks that have been a challenge to over come with this release is
the documentation. Looking over the state of things today, there is
stil
18 matches
Mail list logo
