[Dspace-devel] [DSJ] Issue Comment Edited: (DS-295) CC License being assigned incorrect Mime Type during submission.
[
http://jira.dspace.org/jira/browse/DS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10797#action_10797
]
Stuart Lewis edited comment on DS-295 at 11/14/09 6:28 AM:
---
Some comments:
- the MIME type needs to be set to text/html; charset=utf-8 otherwise some of
the characters in the CC licence don't come through correctly
- Upgrade instructions need to include:
INSERT INTO bitstreamformatregistry (bitstream_format_id, mimetype,
short_description, description, support_level, internal) VALUES
(nextval('bitstreamformatregistry_seq'), 'text/html; charset=utf-8', 'CC
License', 'Item-specific Creative Commons license agreed upon to submission',
'1', true);
UPDATE bitstream SET bitstream_format_id = (SELECT bitstream_format_id FROM
bitstreamformatregistry WHERE short_description = 'CC License') WHERE name =
'license_text' AND source = 'org.dspace.license.CreativeCommons';
Does anyone have any objections to this fix being applied for 1.6?
was (Author: stuartlewis):
Some comments:
- the MIME type needs to be set to text/html; charset=utf-8 otherwise some of
the characters in the CC licence don't come through correctly
- Upgrade instructions need to include:
INSERT INTO bitstreamformatregistry (bitstream_format_id, mimetype,
short_description, description, support_level, internal) VALUES
(nextval('bitstreamformatregistry_seq'), 'text/html; charset=utf=8', 'CC
License', 'Item-specific Creative Commons license agreed upon to submission',
'1', true);
UPDATE bitstream SET bitstream_format_id = (SELECT bitstream_format_id FROM
bitstreamformatregistry WHERE short_description = 'CC License') WHERE name =
'license_text' AND source = 'org.dspace.license.CreativeCommons';
Does anyone have any objections to this fix being applied for 1.6?
> CC License being assigned incorrect Mime Type during submission.
>
>
> Key: DS-295
> URL: http://jira.dspace.org/jira/browse/DS-295
> Project: DSpace 1.x
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.6.0
>Reporter: Steven Williams
>Assignee: Stuart Lewis
> Attachments: bitstream-format.patch, CreativeCommons.patch
>
>
> The Creative Commons License is sharing the Default License Format with a
> mime type of text/plain, but the CC License bitstream should have a mime type
> of text/html. Browsers that render the CC License depending on the mime type
> will display the raw HTML/CSS making the CC License unreadable for the
> average user. To correct this issue a new format needs to be created for the
> Creative Commons License and the submission process needs to assign the new
> format. The attached CreativeCommons.patch replaces the assigned "License"
> format with a "CC License" form.
> Location to apply patch:
> dspace-api/src/main/java/org/dspace/license/CreativeCommons.java
> The attached bitstream-formats.xml adds the new CC License format with mime
> type text/html. This will insure the format is created when dspace is
> installed.
> Location to apply patch: dspace/config/registries/bitstream-formats.xml
>
> Credit also goes to Ladd Hanson
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] [DSJ] Commented: (DS-295) CC License being assigned incorrect Mime Type during submission.
Hi Wendy,
Thanks for spotting that - slippy fingers on my part. I'll update the JIRA
issue comment.
Thanks,
Stuart
From: Wendy Bossons [wboss...@mit.edu]
Sent: Saturday, 14 November 2009 9:04 a.m.
To: dspace-devel@lists.sourceforge.net
Subject: Re: [Dspace-devel] [DSJ] Commented: (DS-295) CC License being assigned
incorrect Mime Type during submission.
No objections, but the sql should be corrected to read "UTF-8", rather than
"UTF=8". Whereas the change will allow the license to display, the character
encoding will be off for characters beyond the ascii character set range.
Example:
[
http://jira.dspace.org/jira/browse/DS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10797#action_10797
]
. . .
INSERT INTO bitstreamformatregistry (bitstream_format_id, mimetype,
short_description, description, support_level, internal) VALUES
(nextval('bitstreamformatregistry_seq'), 'text/html; charset=utf=8', 'CC
License', 'Item-specific Creative Commons license agreed upon to submission',
'1', true);
UPDATE bitstream SET bitstream_format_id = (SELECT bitstream_format_id FROM
bitstreamformatregistry WHERE short_description = 'CC License') WHERE name =
'license_text' AND source = 'org.dspace.license.CreativeCommons';
Does anyone have any objections to this fix being applied for 1.6?
Insert should read:
INSERT INTO bitstreamformatregistry . . . mimetype. . . l) VALUES (. . .
'text/html; charset=utf-8' . . . );
CC License being assigned incorrect Mime Type during submission.
I am unfamiliar with "UTF=8". As far as I know it is not standardized usage.
After running the query on my local development instance, the CC License mime
type was corrected, but the Character set definition was incorrect. When I
changed it to UTF-8, the issue was corrected.
..\Wendy
Wendy Bossons
Web Developer
Contact Information:
wboss...@mit.edu
617-253-0770
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Updated: (DS-366) ora-00942 when running ant fresh install and no metadata saved when submitting a naew item
[ http://jira.dspace.org/jira/browse/DS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry Stone updated DS-366: --- Attachment: lcs_fresh_install.log I tried this with the following stack: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 (server is Linux or Solaris, not sure) Sun Java 1.5.0_16 MacOS 10.5 DSpace 1.5.2 from the binary installation tarball See lcs_fresh_install.log for results.. looks like exactly the same ORA-00942 errors, whcih are inconsequential because that's just the browse index initialization trying to drop tables that aren't there and not caring. The ORA-01408 errors come from two indexes, EPERSON_EMAIL_IDX and EPERSON_NETID_IDX, which cannot be created because there is _already_ an index created automatically on each of those columns when they are declared "UNIQUE". So, those are also inconsequential. I created a sample Collection and submitted a couple of test Items, using all the built-in defaults for submission pages. The metadata I entered was visible in the Describe page, and looked the same after going back to the License page and forward again, and skipping around other pages in teh sausage menu later. It behaved the same in JSPUI, although I mostly tested XMLUI. All I can think of is that the original failure might be tied to a locale choice - perhaps the metadata was entered without a language and when the Describe page tried to show it, it looked for metadta values under the browser locale? > ora-00942 when running ant fresh install and no metadata saved when > submitting a naew item > -- > > Key: DS-366 > URL: http://jira.dspace.org/jira/browse/DS-366 > Project: DSpace 1.x > Issue Type: Bug >Affects Versions: 1.5.2 > Environment: Windows server 2003 + Oracle 10g >Reporter: Vernédal >Assignee: Larry Stone >Priority: Critical > Attachments: 3-ant_fresh_install.log, lcs_fresh_install.log > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > When i submit a new item in a collection, no metadata are saved, even before > i have to confirm submission they are shown "null" > These metadatas are stored in my database ( METADATAVALUE table ) but are not > displayed before confirm submission or when i try to edit the file ( null > appear each time ) > And "null pointer exception " in dspace.log > I noticed that the fresh install processus end with BUILD successfull, > dispite "ORA-00942: Table ou vue inexistante" in the log . These "ora- " > doesn't come from the database_schema.sql wich has been correctly execute. > I have tried the same install with postgresql => everything is correct > It seems to be an oracle issue > has Anyone faced that issue ? > where can i find some statistics about usage of dspace => % of > linux/postgresql % of linux/oracle % of Windows/postgresql % of > windows/oracle => it would be a way for me to justify postgresql usage ( more > supported ) > ( sorry for my english :-( ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Updated: (DS-377) Add META tags identifying DSpace source version to Web UIs
[ http://jira.dspace.org/jira/browse/DS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry Stone updated DS-377: --- Attachment: (was: version-meta.patch.txt) > Add META tags identifying DSpace source version to Web UIs > -- > > Key: DS-377 > URL: http://jira.dspace.org/jira/browse/DS-377 > Project: DSpace 1.x > Issue Type: New Feature > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.6.0 >Reporter: Larry Stone >Assignee: Larry Stone >Priority: Minor > Fix For: 1.6.0 > > > Add a META tag to the HTML generated for each web-UI page that identfies the > version of the DSpace source running on the site. This lets administrators > and developers tell at a glance what their test servers are running, and > curious visitors see what version of DSpace is behind a production site. > The change is very simple and automated in action. Maven is already doing > property-substitution on the dspace.cfg file, so let it plug in the verison > of the "dspace" project (under group "org.dspace"), which should always be > the same as the released or snapshot project for the source tree. From there > it's a simple matter of putting it in a pageMeta element for the XMLUI. > NOTE: This still needs a volunteer to either implement it for JSPUI or point > out the most efficient way to do -- I'll be happy to code and test but I > don't know the JSPUI well enough to spot the most effective place to put a > META tag that goes on every page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Updated: (DS-377) Add META tags identifying DSpace source version to Web UIs
[
http://jira.dspace.org/jira/browse/DS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry Stone updated DS-377:
---
Attachment: version-meta.patch.txt
New, and final, version of the patch.. This one grabs the version from
dspace-api's pom.properties (thanks, Mark!) and adds it to the META
name="Generator" tag in both UIs. Since this is all we need right now, I'm for
keeping the change as small as practical.
org.dspace.app.util.Util.getSourceVersion() returns e.g. "1.6.0-SNAPSHOT"
It appears to be possible to just add properties files under main/resources and
use the plugin in the POM to interpolate properties ("filter").
There is also the JAR manifest file, which can be adjusted in the POM. That
leaves enough room for future adventures.
> Add META tags identifying DSpace source version to Web UIs
> --
>
> Key: DS-377
> URL: http://jira.dspace.org/jira/browse/DS-377
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Affects Versions: 1.6.0
>Reporter: Larry Stone
>Assignee: Larry Stone
>Priority: Minor
> Fix For: 1.6.0
>
> Attachments: version-meta.patch.txt
>
>
> Add a META tag to the HTML generated for each web-UI page that identfies the
> version of the DSpace source running on the site. This lets administrators
> and developers tell at a glance what their test servers are running, and
> curious visitors see what version of DSpace is behind a production site.
> The change is very simple and automated in action. Maven is already doing
> property-substitution on the dspace.cfg file, so let it plug in the verison
> of the "dspace" project (under group "org.dspace"), which should always be
> the same as the released or snapshot project for the source tree. From there
> it's a simple matter of putting it in a pageMeta element for the XMLUI.
> NOTE: This still needs a volunteer to either implement it for JSPUI or point
> out the most efficient way to do -- I'll be happy to code and test but I
> don't know the JSPUI well enough to spot the most effective place to put a
> META tag that goes on every page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] [DSJ] Commented: (DS-295) CC License being assigned incorrect Mime Type during submission.
No objections, but the sql should be corrected to read "UTF-8", rather
than "UTF=8". Whereas the change will allow the license to display,
the character encoding will be off for characters beyond the ascii
character set range.
Example:
[ http://jira.dspace.org/jira/browse/DS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10797#action_10797
]
. . .
INSERT INTO bitstreamformatregistry (bitstream_format_id, mimetype,
short_description, description, support_level, internal) VALUES
(nextval('bitstreamformatregistry_seq'), 'text/html; charset=utf=8',
'CC License', 'Item-specific Creative Commons license agreed upon to
submission', '1', true);
UPDATE bitstream SET bitstream_format_id = (SELECT
bitstream_format_id FROM bitstreamformatregistry WHERE
short_description = 'CC License') WHERE name = 'license_text' AND
source = 'org.dspace.license.CreativeCommons';
Does anyone have any objections to this fix being applied for 1.6?
Insert should read:
INSERT INTO bitstreamformatregistry . . . mimetype. . . l) VALUES
(. . . 'text/html; charset=utf-8' . . . );
CC License being assigned incorrect Mime Type during submission.
I am unfamiliar with "UTF=8". As far as I know it is not standardized
usage. After running the query on my local development instance, the
CC License mime type was corrected, but the Character set definition
was incorrect. When I changed it to UTF-8, the issue was corrected.
..\Wendy
Wendy Bossons
Web Developer
Contact Information:
wboss...@mit.edu
617-253-0770
smime.p7s
Description: S/MIME cryptographic signature
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Created: (DS-382) Proposal: Add 'dc.creator' to Author browse index by default
Proposal: Add 'dc.creator' to Author browse index by default Key: DS-382 URL: http://jira.dspace.org/jira/browse/DS-382 Project: DSpace 1.x Issue Type: Improvement Affects Versions: 1.5.2, 1.5.1, 1.5.0 Environment: any Reporter: Tim Donohue Assignee: Tim Donohue Priority: Minor Fix For: 1.6.0 I'd like to propose that we add the 'dc.creator' metadata field to the Author Browse index in out-of-the-box DSpace. This would also be more consistent with our Search Index (which indexes 'dc.creator' as an Author already by default). Currently, in DSpace 1.5.x, the Browse Configuration in dspace.cfg only indexes 'dc.contributor.*' fields as Authors: webui.browse.index.2 = author:metadata:dc.contributor.*:text I'd like to suggest we make the very minor change to also index 'dc.creator': webui.browse.index.2 = author:metadata:dc.contributor.*,dc.creator:text I can commit this change in preparation for 1.6 assuming others agree that this seems like a reasonable setting for out-of-the-box DSpace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-362) Alphabetization broken in author browse; disregards spaces?
[ http://jira.dspace.org/jira/browse/DS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10807#action_10807 ] Tim Donohue commented on DS-362: I've added this same list of names to an out-of-the-box DSpace 1.5.2 installation. I've verified they are alphabetized in the correct order. Here's the ordering from Dspace 1.5.2 out-of-the-box: Cho, Yoonyoung Chou, Richard M. Choudhury, Anindo Choudoir, Christopher Chounard, Edward Chousal, L. Chow, D. Chowdhury, Mashrur Choy, Young Bin So, it looks like the problem may have to do with Dorothea's setup or configurations? > Alphabetization broken in author browse; disregards spaces? > --- > > Key: DS-362 > URL: http://jira.dspace.org/jira/browse/DS-362 > Project: DSpace 1.x > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.1 >Reporter: Dorothea Salo >Assignee: Tim Donohue >Priority: Minor > Attachments: authorbrowse.png > > > Browsing by author in XMLUI yields strange alphabetization. E.g. from > mi...@uw (screenshot attached): > Choudhury, Anindo > Choudoir, Christopher > Chounard, Edward > Chou, Richard M. > Chousal, L. > Chow, D. > Chowdhury, Mashrur > Cho, Yoonyoung > Choy, Young Bin > What seems to be happening is that the indexer is running words together > (ignoring spaces) and then alphabetizing. Correct behavior (at least in > English) would be putting word-boundary before "a". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Created: (DS-381) community and collection homepage
community and collection homepage - Key: DS-381 URL: http://jira.dspace.org/jira/browse/DS-381 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.6.0 Reporter: Ben Bosman Assignee: Ben Bosman Priority: Minor In the community and collection homepage, the center box contains a "browse by" title. The links contained in that box are static, and not at all dependent on the configured browse lists. This implies there is a difference in the list present here, and the list present in the navigation sidebar, and this can also cause broken links if one of the standard browse lists is not defined in dspace.cfg. This is very easy to fix, and I'm willing to do this, but I'm not sure whether this is at this point still allowed for DSpace 1.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-362) Alphabetization broken in author browse; disregards spaces?
[ http://jira.dspace.org/jira/browse/DS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10806#action_10806 ] Tim Donohue commented on DS-362: I had a discussion with Dorothea about this problem yesterday. I suggested they try and run a complete re-index ( [dspace]/bin/index-init ) to see if that helps resolve the sorting issues. Dorothea said she'd also send along their browse configurations (from dspace.cfg), just to see if anything seems "odd" there. Once I get a chance, I will run the same test as Stuart did on out-of-the-box DSpace 1.5.2. That way we should be able to better tell if this is somehow related to DSpace 1.5.x, or if it's more related to Dorothea's setup/configs. > Alphabetization broken in author browse; disregards spaces? > --- > > Key: DS-362 > URL: http://jira.dspace.org/jira/browse/DS-362 > Project: DSpace 1.x > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.1 >Reporter: Dorothea Salo >Assignee: Tim Donohue >Priority: Minor > Attachments: authorbrowse.png > > > Browsing by author in XMLUI yields strange alphabetization. E.g. from > mi...@uw (screenshot attached): > Choudhury, Anindo > Choudoir, Christopher > Chounard, Edward > Chou, Richard M. > Chousal, L. > Chow, D. > Chowdhury, Mashrur > Cho, Yoonyoung > Choy, Young Bin > What seems to be happening is that the indexer is running words together > (ignoring spaces) and then alphabetizing. Correct behavior (at least in > English) would be putting word-boundary before "a". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-377) Add META tags identifying DSpace source version to Web UIs
[
http://jira.dspace.org/jira/browse/DS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10805#action_10805
]
Mark Wood commented on DS-377:
--
I agree that this should NOT be stored in dspace.cfg -- it is not configuration
data and shouldn't be offered for modification by the sysadmin.
I note that Maven is already producing a Properties file with the version in
it, which you can see thus:
import java.io.InputStream;
import java.io.IOException;
import java.util.Properties;
class VersionTest
{
public static void main(String[] argv)
throws java.io.IOException
{
InputStream cis = VersionTest.class.getResourceAsStream
("/META-INF/maven/org.dspace/dspace-api/pom.properties");
Properties constants = new Properties();
constants.load(cis);
System.out.println("version " + constants.get("version"));
}
}
However that only helps us with a handful of Maven properties, and we might
want other things later on. We might be better off adding a
dspace-api/src/main/resources/constants.properties to be filtered and wrapped
into dspace-api-VERSION.jar.
Also I recommend that the value be a pure version number. It's easier to
supply the literal "DSpace" where we want it than to parse the version out of a
more complex string where we want only the version. That is, it should be the
value of ${project.version}.
> Add META tags identifying DSpace source version to Web UIs
> --
>
> Key: DS-377
> URL: http://jira.dspace.org/jira/browse/DS-377
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Affects Versions: 1.6.0
>Reporter: Larry Stone
>Assignee: Larry Stone
>Priority: Minor
> Fix For: 1.6.0
>
> Attachments: version-meta.patch.txt
>
>
> Add a META tag to the HTML generated for each web-UI page that identfies the
> version of the DSpace source running on the site. This lets administrators
> and developers tell at a glance what their test servers are running, and
> curious visitors see what version of DSpace is behind a production site.
> The change is very simple and automated in action. Maven is already doing
> property-substitution on the dspace.cfg file, so let it plug in the verison
> of the "dspace" project (under group "org.dspace"), which should always be
> the same as the released or snapshot project for the source tree. From there
> it's a simple matter of putting it in a pageMeta element for the XMLUI.
> NOTE: This still needs a volunteer to either implement it for JSPUI or point
> out the most efficient way to do -- I'll be happy to code and test but I
> don't know the JSPUI well enough to spot the most effective place to put a
> META tag that goes on every page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-380) Spanish Translations on "Describe Item" when submitting new item
[ http://jira.dspace.org/jira/browse/DS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10804#action_10804 ] Miguel Carro Pellicer commented on DS-380: -- I have input-forms.xml translated and working in Spanish, how can i contribute with Dspace providing the translation? > Spanish Translations on "Describe Item" when submitting new item > > > Key: DS-380 > URL: http://jira.dspace.org/jira/browse/DS-380 > Project: DSpace 1.x > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.5.2 >Reporter: Miguel Carro Pellicer > Attachments: I18N-2.JPG, I18N.JPG > > > Setting spanish as a default language, when submitting a new item, english > texts appear in "DESCRIBE ITEM" section. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Closed: (DS-380) Spanish Translations on "Describe Item" when submitting new item
[ http://jira.dspace.org/jira/browse/DS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudia Jürgen closed DS-380. - Documentation Status: Not Required (was: In Attachment(s)) Resolution: Won't Fix Hello, the text which appear during the submission is not part of the Messages.properties, but of the input-forms.xml. You got to provide a translation of this file as input-forms_es.xml yourself and hopefully contribute it back to the DSpace community. Furthermore there is no (jspui or xmlui) language pack available for DSpace 1.5.2, see current translation status at: http://wiki.dspace.org/index.php/I18nSupport#Available_translations_of_Messages.properties_for_JSP-UI So you might encounter other missing language tags. The latest translation for both UI's is 1.5.1. If you are working on 1.5.2, it would be great if you 'll find the time to update the available translations. Sunny Greetings Claudia Jürgen > Spanish Translations on "Describe Item" when submitting new item > > > Key: DS-380 > URL: http://jira.dspace.org/jira/browse/DS-380 > Project: DSpace 1.x > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.5.2 >Reporter: Miguel Carro Pellicer > Attachments: I18N-2.JPG, I18N.JPG > > > Setting spanish as a default language, when submitting a new item, english > texts appear in "DESCRIBE ITEM" section. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Created: (DS-380) Spanish Translations on "Describe Item" when submitting new item
Spanish Translations on "Describe Item" when submitting new item Key: DS-380 URL: http://jira.dspace.org/jira/browse/DS-380 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.2 Reporter: Miguel Carro Pellicer Attachments: I18N-2.JPG, I18N.JPG Setting spanish as a default language, when submitting a new item, english texts appear in "DESCRIBE ITEM" section. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Integrating Dspace in a LMS
Hi subscribers! I want to know what kind of mechanism implements Dspace to communicate with other systems. (WebServices, SOAP, WSDL, etc) Very grateful Miguel. -- Miguel Carro Pellicer mca...@pentec.es +34 - 96 393 74 33 ext. 32 www.samoo.es Este correo y sus archivos asociados son privados y confidenciales y va dirigido exclusivamente a su destinatario. Si recibe este correo sin ser el destinatario del mismo, le rogamos proceda a su eliminación y lo ponga en conocimiento del emisor. La difusión por cualquier medio del contenido de este correo podría ser sancionada conforme a lo previsto en las leyes españolas, Ley Orgánica 15/1999 de Protección de Datos de Carácter Personal. No se autoriza la utilización con fines comerciales o para su incorporación a ficheros automatizados de las direcciones del emisor o del destinatario.” This mail and its attached files are confidential and are only and exclusively intended to their addressee. In case you may receive this mail not being its addressee, we beg you to let us know the error by reply and to proceed to destroy it. The circulation by any mean of this mail could be penalised in accordance with the Spanish legislation. Is not allowed the use of both, the transmitter and the addressee’s, address with a commercial aim, or in order to be incorporated to automated data process or to any kind of files. P Antes de imprimir este correo electrónico piense bien si es necesario hacerlo. El medioambiente es cosa de todos. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-379) open-search in jspui won't return description.xml
[ http://jira.dspace.org/jira/browse/DS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10802#action_10802 ] Richard Rodgers commented on DS-379: Hi Stuart - I'm away from my desk till next week - but it looks OK - I'd only check whether the servlet is defensive enough about non-description URLs like /open-search/foo.xml Thanks, Richard > open-search in jspui won't return description.xml > - > > Key: DS-379 > URL: http://jira.dspace.org/jira/browse/DS-379 > Project: DSpace 1.x > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.0 >Reporter: Stuart Lewis >Assignee: Richard Rodgers > Fix For: 1.6.0 > > > In web.xml, open-search is only set to respond to /open-search so it gives a > 404 when /open-search/description.xml is requested. > Changing the servlet mapping from: > > open-search > /open-search > > to > > open-search > /open-search/* > > seems to fix it. > Could you confirm if this is OK to change Richard? Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
