[
http://jira.dspace.org/jira/browse/DS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11026#action_11026
]
Stuart Lewis commented on DS-295:
---------------------------------
stuartlewis: http://jira.dspace.org/jira/browse/DS-295
[09:49am] stuartlewis: Read the last comment.
[09:50am] stuartlewis: We can most cleanly add some new bitstream formats by
including a new file containing just those two.
[09:50am] stuartlewis: But this file will just be for "upgraders".
[09:50am] stuartlewis: We don't have any upgrade files other than the db
upgrade scripts.
[09:50am] stuartlewis: So where should other upgrade files go?
[09:51am] lcs: the file could go in config/registries with an "upgrade" name so
it's with the others.
[09:51am] stuartlewis: dspace/etc/upgrade-files/15-16/ ?
[09:51am] richardrodgers: sure
[09:51am] stuartlewis: I'm happy with either suggestion
[09:52am] lcs: a separate upgrade-files subdir is more tidy but wouldn't it
take a lot of doc changes?
[09:52am] stuartlewis: lcs: No - as this is the only upgrade file so far
(assuming we leave the db upgrade files where they are)
[09:52am] grahamtriggs: action for future - ideally, we should just have a
single 'current' version of these registries, and tools that compare with an
existing installation, add new entries (possibly remove old ones that aren't
referenced)
[09:53am] mdiggory: For one of the upgrades theres actually java classes that
are executed, like...
[09:53am] lcs: ah, i was thinking that the whole beauty of it is that future db
upgrade files would go there too, but that gets complicated with oracle/pgsql..
[09:53am] mdiggory:
https://scm.dspace.org/svn/repo/dspace/trunk/dspace-api/src/main/java/org/dspace/administer/Upgrade11To12.java
[09:53am] tdonohue: seems reasonable to keep in separate upgrade-files folder.
maybe we can eventually figure out a way to move the db upgrade files there as
well
[09:53am] stuartlewis: Ok - so shall I create that dir, and use it just for
this file for now?
[09:53am] mdiggory: I wonder if we should have a more java centric upgrade
process here...
[09:54am] stuartlewis: "dsrun org.dspace.upgrade 1.5 1.6"?
[09:54am] mhwood: No objection here.
[09:54am] stuartlewis: ...but we can leave that for 1.7
[09:55am] stuartlewis: Ok - I'll do that then.
[09:55am] stuartlewis: Any other issues on that list that need talking about?
[09:55am] tdonohue: or even better "dspace upgrade 1.6 1.7" - sounds like
something for 1.7
[09:55am] mdiggory: true... I just think the config / etc dirs are getting a
bit out of hand
[09:55am] lcs: maybe call the directory dspace/etc/upgrades/ since files is
kind of assumed
[09:55am] stuartlewis: lcs: Good point
> 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
> Fix For: 1.6.0
>
> Attachments: add-cc-license.xml, bitstream-format.patch,
> CreativeCommons.patch, DS-295-updated.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
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
