Hi all,
We're on version 3.2 using the xmlui with a postgres database.
We recently migrated from 5.2, and had done some work to alter our legacy
custom embargo system to be more-or-less compatible with the newer policy-based
embargo system (described in DS-108). We had some issues stemming from the fact
that the description attribute in the resourcepolicy table is a varchar(100)
while our legacy system stored the reason in an unlimited text field. While we
rarely need more, limiting the reason to one hundred characters has caused some
workflow issues for some of our users. Also, as it comes out of the box, the
dspace master throws an uncaught PSQLException when a reason longer than 100
characters is entered during the submission access step (we've been avoiding
the exception through form validation). We were considering logging a ticket to
ask that the fields type be changed to 'text' or expanded to a wider varchar.
As a preliminary to logging said ticket, I wanted to ask a few questions here:
Does anyone know why the resourcepolicy.rpdescription field is limited to 100
characters?
Are there any other bugs on the Jira that might be related to this?
Thanks,
Seth Robbins
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
