Thanks Paulo,
I went on vacation after we had the conference call and it slipped my
mind to post the results. We discussed the options for this patch and
decided that because there are no modularity options for the JSPUI,
and the administrative interface in the XMLUI that this patch can
. Let's try to
plan something in the next week if possible. I will also consider if
some of this can fit into my presentation as an example.
On Thu, Apr 30, 2009 at 7:07 AM, Mark H. Wood mw...@iupui.edu wrote:
On Wed, Apr 29, 2009 at 03:47:12PM -0500, Scott Phillips wrote:
You make some good
Mark,
You make some good points here about the patch. I think it may be
possible to find some time to refactor the patch in the ways you are
suggesting. The problem is similar to a chicken and an egg, which came
first. There are challenges to developing addons like you suggest with
the
The Minho stats package does not integrate with the XMLUI in any
version. You must run the JSPUI in order to view and analyze the
statistics. The confusion around this steams from misleading
statements about the packages ability to read logs generated from the
XMLUI.
Scott--
On Apr 3,
We never created a place to store images that are references in
Aspects. We were never able to come up with a reason when an aspect
would need to do this. That's not categorical, it's just we couldn't
think of one so we put off the problem until it actually presented
itself. In all the
Ricardo,
Does the university of Minho plan on developing XMLUI compatibility
(i.e. the ability to view statistics from Manakin) in a future release
of the statistics addon?
Scott--
On Feb 19, 2009, at 11:17 AM, Ricardo Otelo Santos Saraiva Cruz wrote:
Hi,
There has been a bit of
John,
Down here in Texas we also face this challenge to create a federated
repository among all institutional repositories across the state. Up
until now we've been doing a manual federation process which includes
dspace imports and exports plus some scripts that work on those
exports.
Eric,
The ability to provide additional CSS files for specific browsers is
meant to simplify your life not make it hell - sorry about that. First
look at the global sitemap.xmap at the root of the webapp around line
136 you should find something like the following:
map:selector
Technically you can put you're theme anywhere you want so long as the
tomcat process has read access to the location and you adjust the
xmlui.xconf appropriately. Most people just place their themes inside
the source tree under the themes/ directory while developing it. Once
you're ready
yes, there are some cache issues with Manakin 1.1 on DSpace 1.4.2,
somewhere way back in the email archive for dspace-dev there is a
patch that fixes the issue... Or alternatively you could update to
DSpace 1.5.0 or 1.5.1... And finally if it's not going to cause
problems you can just
You may want to look at a Journal collection we've done. It doesn't
completely address the problem you're asking about but is in the same
sphere, and i second what Mark said, it is likely best to not use
communities and collections in that manor.
Geetha,
This feature is available to allow community and collection
administrators to download a copy of their collection. This allows
them to take their content and move to another system if they wish, or
in one case we have here run a local DSpace instance with the
collection.
Scott--
DSpacers,
It's a funny thing, the DSpace Batch Import Format (of which there are
two) are not documented anywhere other than looking at the source
code. We've run across the situation where a department has some
content to put into the repository and the resources to create a batch
We wanted to expose dspace's metadata in a way that can be used by
other applications. They are nice restfull urls that are actionable
and easily predictable. There are a few themes that will do client
side parsing of those urls in javascript, it opens the possibility for
other things to
There will be no future releases of a stand alone version of Manakin.
Anyone who is using Manakin 1.1 should move to DSpace 1.5 with
integrated Manakin.
Scott--
On Jun 25, 2008, at 7:53 AM, Mark H. Wood wrote:
Where should one send patches for Manakin 1.1? Yeah, we should be
moving to
Use the URLs:
handle/123456789/9?XML
handle/123456789/9?show=fullXML
Scott--
On Apr 21, 2008, at 12:04 PM, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
so, my metadata appears in full item view (url -
handle/123456789/9?show=full) and if i append ?XML nothing happens.
i can get xml with
Oh, sorry. I thought have thought a step a head in answering your
question. Yes, adding the XML will give you the DRI page. However the
DRI page no longer includes proper metadata, instead it includes a
reference to the metadata. So you see the line:
reference repositoryID=123456789
Can you explain where, what fields were giving you the incorrect
encoding? Also what is your setup - are you using Tomcat or Apache
with AJP? Did you remember to set your tomcat connector's URIencoding
to UTF-8?
Scott--
On Apr 16, 2008, at 8:42 AM, BAILLY, Vincent wrote:
Hello,
I
George,
This been an often requested feature that is well suited for Manakin.
I know several people have it on their to-do list but none have
started working on a project of this type. I think several would
appreciate Edinburgh being able to take the lead on this.
Scott--
On Apr 7,
that is persisting individual ratings, compiling
them and presenting recommendations must surely be deeper...
Scott Phillips wrote:
George,
This been an often requested feature that is well suited for Manakin.
I know several people have it on their to-do list but none have
started working
One strategy you may want to adopt, is to include a reference to a
steaming sever in your items metadata. Then have your theme display
that link as the file to download. This way you can separate all re
technology you need to run a proper streaming sever from your
repositry which doesnt
Everyone,
There have been some build problems identified with the recent release
of sword in dspace 1.5, below you will find a set of alternative build
instructions to solve these problems.
cd [dspace-source]/dspace-sword/
mvn -Ddspace.config=/path/to/dspace.cfg package
cd
has started handling Continuous Integration on the
1.5.x branch... this includes producing interim builds of the
releases... so another alternative could be to direct users to work
with those as an alternative to using the release until we cut 1.5.1
-Mark
On Mar 29, 2008, at 11:59 AM, Scott
Previously on SourceForge versions older than 2 or 3 releases had been
tagged as hidden. I corrected that when I put up the 1.5 release
because it made sense that all stable releases should be public, and
only old beta alphas are hidden.
However the previous advice is correct, all you
Rick,
Thank you for the bug report. Unfortunately this patch did not make it
into the 1.5 release, which occurred earlier (before the original
email). The announcement of the release will be going out tomorrow
morning. The release has been picked up and is in the Central Maven
Repository
and database issues, and Mark Diggory for resolving build
problems.
Scott Phillips
Research and Development Coordinator
Texas Digital Library and Texas AM University Libraries
[EMAIL PROTECTED]
-
Check out the new
javascript would need to be at the theme layer. By default Manakin
will provide set the RSS feeds in the HTML header and most browsers
will put an icon at the end of the URL bar for them. If you would like
to change this behavior then you will need to customize it in a theme.
Scott--
On
This may not help your problem with 1.1a, but I looking in DSpace 1.5
and it has the same unprotected NPE problem. I've committed a fix for
that it but I am unable to test LDAP so there may be other problems
past that.
Scott--
On Mar 14, 2008, at 6:08 AM, Mika Stenberg wrote:
I just
George,
Thank you for finding and solving this bug - I have committed a fix
into the 1.5 branch. I also place a default news-xmlui.xml file for
those doing a fresh install so that they will have an example copy to
modify. Here's the default that I supplied:
?xml version=1.0 encoding=UTF-8
.
Download Link:
http://sourceforge.net/project/showfiles.php?group_id=19984package_id=267976release_id=585287
Scott--
On Mar 10, 2008, at 10:01 PM, Scott Phillips wrote:
DSpace Community,
The second beta release of DSpace 1.5 is now available on
SourceForge.net. There is no test-a-thon
a few hours before
updating.
On Feb 7, 2008, at 12:58 AM, Scott Phillips wrote:
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
Reuben,
See my answers below:
On Mar 6, 2008, at 9:20 AM, Reuben Pasquini wrote:
Hello!
We're evaluating several packages
for setting up an institutional repository.
I'm very impressed with D-Space, but have
a few questions - hope the list can help me out.
*. It looks like manakin
Not that I know of. The development path as I understand it is moving
away from JSP altogether, in the direction of Manakin. I don't know
how I'd throw a Dreamweaver dev at Manakin; I suppose I might throw a
webcrawler at my Manakin instance and pass over the resulting HTML/CSS
to them, but
Have you tried using the pdffilter.largepdfs and
pdffilter.skiponmemoryexception parameters?
Turning on largepdfs will tell pdfbox to use a temporary file while
processing the pdf instead of keeping it all in memory. It will use
the standard java.io.tmpdir directory to store them in. In
-B702)[NCI
INFORMATION SYSTEMS] wrote:
Hi Scott,
Thanks for the info, but can you tell me exactly where to put/
how to format the parameters? Do they go on the dsrun command?
Thanks again,
Sue
From: Scott Phillips [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2008 6:51 PM
Everyone,
Alexey, our Manakin theme guru here at AM, has posted a new Manakin
theme tutorial on the wiki. I hope this will help out those who are in
the process of creating their own themes. It covers the basic
mechanism of creating a new theme, some helpful paradigms on how to
tackle
The DSpace authorization system is showing it's age and has several
problems that have remained unaddressed. In my opinion the principle
problem is that it does not recognize the difference between a role
and a permission. Where a role is something like submitter, or
administrator, and
DSpace Community,
One of the major upgrades that is forthcoming with the 1.5 release of
DSpace is a new Maven-based build system. I wanted to take some time
to explain why we have made this choice and what it means for the
community. Maven is a software tool from the Apache Foundation that
Fellow DSpacers,
The first beta for DSpace 1.5 has been released. You may either
checkout the new tag directly from SVN or download the release from
sourceforge. One sourceforge you will not that there are two types of
releases:
dspace-1.5.0-beta1-release
dspace-1.5.0-beta1-src-release
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
Yinjin,
When you add ?XML to the end of a url you adding an extra URL
parameter this works when there are no other parameters in the url
string (i.e. there already exists an ? in the url string). In this
case you need to add XML to the end of the parameter. The ? character
says starts a
Ying,
The advanced search component could be nice to have it configurable...
in the sense that it follows the jspui i.e. listening to the index
configuration. It could also be more configurable to make it easier
for themes to add new indexs and field types.
However right now I am not
Terry,
Short answer: no.
Manakin doesn't support the controlled vocabularies plugin, mostly
because it uses a pop-up window which are hard to deal with. I
understand that there is or may be a project at the University of
North Texas to solve this problem.
Scott--
On Jan 10, 2008, at
. item metadata on the item page).
Correct?
-sf
On Jan 4, 2008, at 10:38 AM, Scott Phillips wrote:
Sands,
Manakin does not have a template per page, so there is not a
template to be found for a particular page.
The set of templates used to transform a page are determined based
Mika + Tim,
I was under the impression that the two xml files had been merged
together so you only need one supported by either XMLUI or JSPUI? The
XMLUI only adds an extra tag in it for which presentation class to use.
Tim can you shed any light on this?
Scott--
On Jan 3, 2008, at 8:07
Dorothea,
This is a good question, and it's a bit open as too what the best
practice is in my opinion. I think it is okay for themes to have
dependencies to other themes as long as that dependency is document
and enforced (preferably through maven).
One concept that we've been using is to
Dorothea,
Sorry for the late reply, catching up on email from the break
I see you've already had your specific problem answered. But I'd like
to chime in with a bit general advise. When doing development with XSL
it's a pain to have it running live on the site as you pointed
out.
Richard,
That's really great, sword looks exciting. In my opinion its release
is too late for inclusion in 1.5. We need to focus on documentation
and testing of what is all-ready a massive release (possibly the
biggest one since 1.0) instead of adding new features and pushing the
release
Scott--
On Nov 2, 2007 3:34 PM, Scott Phillips [EMAIL PROTECTED] wrote:
I propose that we have our first DSpace 1.5 test-a-thon next week on
November 7th. The event would continue all day, across all time zones.
The basic idea is that this day is set aside for people to test the
release, identify
I can add two things,first to reiterate graham point and then to add
we're not by default using xstl 2.0 in manakin, just to keep things
simpiler. However if your theme needs 2.0 it is not hard to add it. We
should probably create the cocoon definition for it and include the
library as a
50 matches
Mail list logo
