[
http://jira.dspace.org/jira/browse/DS-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudia Jürgen resolved DS-567.
---
Documentation Status: Not Required (was: Needed)
Resolution: Fixed
Fix Version/s: 1
[
http://jira.dspace.org/jira/browse/DS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudia Jürgen updated DS-595:
--
Attachment: Messages_cs.properties
Added missing tag, now compliant to 1.6.1.
> Czech localization of 1.6.1
>
[
http://jira.dspace.org/jira/browse/DS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11513#action_11513
]
Claudia Jürgen commented on DS-595:
---
Hello Ivan,
thanks for updating the Czech translation to 1.6.1.
[
http://jira.dspace.org/jira/browse/DS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11515#action_11515
]
Ivan Masár commented on DS-595:
---
Thanks, it's correct.
> Czech localization of 1.6.1
> --
[
http://jira.dspace.org/jira/browse/DS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudia Jürgen updated DS-595:
--
Assignee: Claudia Jürgen
Status: Open (was: Received)
> Czech localization of 1.6.1
> -
[
http://jira.dspace.org/jira/browse/DS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudia Jürgen closed DS-595.
-
Resolution: Fixed
Fix Version/s: 1.6.2
The message catalogues have been committed to the codebase. The ot
On Thu, Jun 10, 2010 at 11:45:49AM -0700, Mark Diggory wrote:
> Did you look over the Quartz Job Scheduler Addon, this type of asynchronous
> thread spawning activity is what I intended it to alleviate us from doing.
I had not thought of it. I was thinking to get the export done
immediately, not
Hello,
We have been migrating our DSpace to 1.6, and are planning to also make an ip
address change that will impact the handle-server.
There was an assumption that the existing handle-server would continue to meet
our needs while we completed miscellaneous required migraton tasks. At this
poi
All,
Just thought I'd bring this up while it's fresh in my mind. A few of us
in DuraSpace got into a license header discussion, and it made me
re-discover our current DSpace license header situation.
Most of our codebase still uses the policy of including the entire
license as a header in a s
Have the Foundation's lawyers examined the proposed change and given
an opinion? or is there one already covering the Fedora practice?
Mechanical details are important, but ultimately the most important
aspect of copyright claims and licensure is whether they work in the
legal context.
If the lawy
The only parts of the installation that care about location seem to be
bin/start-handle-server and the HandlePlugin class that interfaces the
Handle server to DSpace's database. I presume that you're leaving the
old DSpace installation in place (perhaps not running any UI) until you
complete the m
Hi Mark,
Good question.
I'm told the Fedora folks ran their license header solution (referencing
an external file) by lawyers at UVA a few years ago, and they were OK
with it.
Also, again note we are not suggesting any changes to either the DSpace
License or Copyright text. We'll still obvio
+1
We came up with the more concise format last year to reduce the amount of
commenting at the top of the files and to standardize the licensing includes
int he maven release process. The new dspace-pom projects assure that
licensing is always validated on all the files prior to release.
I wi
And per
> (1) We would slowly work to replace our existing license headers with
> this new standard license header. (Or, if possible, do a giant bulk
> replace of our existing headers for the 1.7.0 release)
The license:format plugin in the dspace-pom will facilitate this batch across
the enti
With respect to the live database, do you mean the dsp...@mit production
database or a flat file database that, perhaps, the handle-server uses? If the
latter, how would I configure this? (I am not familiar with the running of the
handle-server yet, so I am not sure how all the pieces fit toget
The handle server uses the HandleManager as a plugin to bridge the dspace
database into the handle service. The Handle Server doesn't store handles
internally. Its all in the postgres db at the moment.
Mark
On Jun 11, 2010, at 11:00 AM, Wendy J Bossons wrote:
> With respect to the live databa
Wendy,
If I'm understanding correctly, your setup before migration/update was
that you had the Handle Server & DSpace running on the same server (and
are using the bundled Handle Server that comes with DSpace, rather than
an external handle server)?
I'd suggest that if you are migrating DSpace
Essentially then, and to hopefully accurately paraphrase Mark W.'s comments . .
.
If the server where dsp...@mit currently resides continues to run, and if we
continue using the same database location, then the handle-server should run.
However, if we move the database to a new location, then t
Wendy,
The Handle server relies on the codebase that is deployed into your
[dspace-dir]/lib so if you are not changing out things to dramatically to
alter the handle server behavior, yes, you should be able to do what your
suggesting if its using the same postgres db, even running the handlese
Here's a different option (that I used to use at Illinois):
(1) Before migration day, notify handle.net folks that you will be
moving to a new server. Ask them nicely if they can update your handle
prefix settings for you on that migration day (you'll need to send an
updated sitebndl.zip befor
additionally...
On Jun 11, 2010, at 11:21 AM, Wendy J Bossons wrote:
> Essentially then, and to hopefully accurately paraphrase Mark W.'s comments .
> . .
>
> If the server where dsp...@mit currently resides continues to run, and if we
> continue using the same database location, then the hand
On Fri, Jun 11, 2010 at 02:21:27PM -0400, Wendy J Bossons wrote:
> Essentially then, and to hopefully accurately paraphrase Mark W.'s comments .
> . .
>
> If the server where dsp...@mit currently resides continues to run,
> and if we continue using the same database location, then the
> handle-se
[
http://jira.dspace.org/jira/browse/DS-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11517#action_11517
]
Peter Dietz commented on DS-604:
The Registry Format Update can be shortened (and to use the dspace laun
Hi Tim,
Thanks for the steps . . . that is where we are headed. I contacted CNRI this
afternoon and had a very positive response with respect to working on our time
table.
cheers,
..\Wendy
Wendy Bossons
Web Developer
MIT Libraries
Technology Research and Development
77 Masachusetts Avenue
Cam
[
http://jira.dspace.org/jira/browse/DS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-608:
Component/s: (was: DSpace API)
(was: JSPUI)
Attachment: [DS-608].patch
> Batch metad
[
http://jira.dspace.org/jira/browse/DS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis resolved DS-608.
-
Resolution: Fixed
Fix Version/s: 1.7
Resolved in 1.6.x branch (for 1.6.2) and in trunk (for 1.7).
> Batc
26 matches
Mail list logo
