Peter Dietz 21cb0e0520 DS-1945 Add request_message to requestitem DB table ...

Also, refactored requestitem to be a dspace-api "model", moved all DB logic
from XMLUI regarding this module to the dspace-api model.

Add the requestitem.request_message to display in the contact-author form,
so they can see what the original request message was.

2014-05-10 08:20:11 -04:00

..

xmlworkflow

[DS-1803] Configurable workflow migration script fails if collection workflow group has been renamed

2013-11-25 13:05:56 +01:00

database_schema_3-4.sql

DS-1811 Removing a collection fails if non-Solr DAO has been used before for item count

2013-12-02 00:26:43 +01:00

database_schema_4_5.sql

DS-1945 Add request_message to requestitem DB table

2014-05-10 08:20:11 -04:00

database_schema_11-12.sql

[DS-297] Move PostgreSQL-specific SQL into etc/postgres for greater clarity

2009-10-09 22:42:19 +00:00

database_schema_12-13.sql

[DS-297] Move PostgreSQL-specific SQL into etc/postgres for greater clarity

2009-10-09 22:42:19 +00:00

database_schema_13-14.sql

[DS-297] Move PostgreSQL-specific SQL into etc/postgres for greater clarity

2009-10-09 22:42:19 +00:00

database_schema_14-15.sql

[DS-297] Move PostgreSQL-specific SQL into etc/postgres for greater clarity

2009-10-09 22:42:19 +00:00

database_schema_15-16.sql

[DS-295] CC License being assigned incorrect Mime Type during submission.

2009-12-20 08:54:06 +00:00

database_schema_16-17.sql

RE: DS-729 (update-sequences.sql script errors out, as it refers to an old, obsolete 'dctyperegistry' table). I'm committing a 'database_schema_16-17.sql' upgrade script, to ensure this old obsolete sequence is removed from existing DSpace databases. It's probably better to remove it now, rather than let it continue to languish around in everyone's DB. This needs to be added as part of the DSpace 1.6 -> 1.7 Upgrade instructions.

2010-10-29 17:10:02 +00:00

database_schema_17-18.sql

Fix Encoding of 1.7 to 1.8 Postgres DB Upgrade script. All other DSpace SQL scripts are encoded in ANSI. This one was encoded in UTF8, which was causing this Postgres bug to occur: http://archives.postgresql.org/pgsql-bugs/2010-03/msg00239.php

2011-10-18 16:42:26 +00:00

database_schema_18-3.sql

Atmire dspace 3.0 versioning contribution

2012-09-20 01:14:30 +02:00

database_schema.sql

DS-1945 Add request_message to requestitem DB table

2014-05-10 08:20:11 -04:00

update-sequences.sql

DS-1916 Error in update-sequence script in 4.0

2014-02-18 15:17:52 +01:00