[
http://jira.dspace.org/jira/browse/DS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-464:
---------------------------
Fix Version/s: 1.n
Assignee: Richard Rodgers
Discussion that occurred during DSpace Dev Meeting on Feb 10, 2010:
[15:45] <tdonohue> http://jira.dspace.org/jira/browse/DS-464 : Item type
based submission
[15:46] <richardrodgers> Good idea, but too late to integrate into an RC
[15:46] <mhwood> Agree.
[15:46] <tdonohue> yea, definitely too late for 1.6, but sounds like a great
idea for later
[15:46] <kshepherd> even if it's not in trunk, could it be up in SVN somewhere?
[15:47] <kshepherd> (is it already?)
[15:47] <tdonohue> it isn't yet, though it could be added to /sandbox/
area....volunteers?
[15:48] <mdiggory> I think we want to look at Item Tpye based submission as a
review project, looking at multiple solutions
[15:48] <mdiggory> because we have seen multiple requests and activities to
create it
[15:48] <richardrodgers> Sure, I was going to work with Robin on this - as
mdiggory says, with multiple options
[15:48] <tdonohue> sounds great, I'll assign DS-464 to richardrodgers then
...
[15:49] <mdiggory> I would like to see an opportunity to really get the
requirements identified before any one solution is selected.
[15:50] <richardrodgers> mdiggory: which are you referring to?
[15:50] <mhwood> Yeah, it sounds like a feature that various people will
imagine differently. We need to surround as many imaginations as is practical.
[15:50] <grahamtriggs> and it could/should be linked to file driven submission
- identification of which leads to different (pre-filled where possible) forms
[15:50] <mdiggory> type based submission
[15:51] <richardrodgers> Ah ok - What I have in mind is an abstraction that
takes any factor and maps to an input
[15:51] <kshepherd> type-based submission is probably the most common request
from my admins since i started my job...
[15:51] <richardrodgers> factor = type, collection, eperson, complex function
of above, etc
[15:52] <grahamtriggs> phase of the moon :)
[15:52] <mdiggory> Not trying to get into the technical discussion here, just
that it would be good to have the discussion
[15:52] <tdonohue> well, based on all this, maybe type-based submission could
be a nice new feature for 1.7 :)
[15:52] <mhwood> Is that a Special Topic or a Proposal?
[15:53] <kshepherd> it's a special topic that might result in a few different
proposals?
[15:53] <mdiggory> mhwood: 9.9
[15:53] <richardrodgers> I'll post a proposal to start, how's that :)
[15:53] <tdonohue> kshepherd has got it. it's a topic, and we need to
investigate on how to implement :)
[15:53] <tdonohue> yep, sounds good richardrodgers
[15:54] <mdiggory> topic "Item Based Submission".... Proposals = possible
solutions.
[15:54] <mdiggory> topic should have some details about the problem domain.
[15:54] <mdiggory> proposals should present solutions to problem domain
[15:55] <tdonohue> thanks mdiggory...that's a good explaination
[15:55] <mdiggory> feel free to copy/paste without attribution ;-)
[15:56] <grahamtriggs> *ahem*... I suggest "Content Driven Submission"... it
has more scope, and is technically a bit more accurate (you can argue all
submissions are already item based!!)
> Item type based submission
> --------------------------
>
> Key: DS-464
> URL: http://jira.dspace.org/jira/browse/DS-464
> Project: DSpace 1.x
> Issue Type: New Feature
> Components: DSpace API, XMLUI
> Affects Versions: 1.5.2
> Reporter: Robin Taylor
> Assignee: Richard Rodgers
> Priority: Minor
> Fix For: 1.n
>
> Attachments: Item-based-Submission.zip
>
>
> This code adds a new screen to the submission process that allows the user to
> select an item type from a list of types defined in the input-forms.xml file.
> The subsequent metadata collection screen(s) are then built based on the
> selected type. The code was developed as an XMLUI Maven module and is
> included in the attached zip file along with a README with installation
> instructions.
> For the techies amongst you :-
> The existing input-forms.xml allows for different forms based on collection
> name or handle, in fact its already more generic than that. The file and
> reader class just expect a string as input so the file can be reformatted
> based on item type. The module comprises a new screen plus some minor changes
> to existing classes to get/set the item type and persist it in the database
> whilst the item is in submission/workflow.
> I haven't included code for a JSPUI screen although if the screen is not
> defined in item-submission.xml then the code will revert to the collection
> based forms. I could provide a JSPUI alternative if there were interest.
> This has been tested at 1.5.2 but I suspect it would work without alteration
> for 1.6. Again, I can test this if there is interest.
--
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
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
