<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-NZ link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Yuri,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m not sure you’re exactly on the right track re: SWORD, but
for what it’s worth I think Graham’s suggestion is excellent, and I wish I’d
known about it before!<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Paulo’s suggestion is similar to something I’ve done, and is
possible to achieve without changing source code or creating new interfaces...
it’s a good idea too. I wonder if there’s a workflow step that can be added to
make the mapping to the “true” collection easier after the “content-type”
collection has been used for submission...<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m now convinced my previous suggestion would be the hardest of
the three to implement, and since you’re only wanting to change one small
aspect of submission, it’s probably worth looking at an internal Dspace solution.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kim<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> dspace-general-bounces@mit.edu
[mailto:dspace-general-bounces@mit.edu] <b>On Behalf Of </b>Yuri<br>
<b>Sent:</b> Thursday, 5 March 2009 7:59 a.m.<br>
<b>To:</b> Graham Triggs<br>
<b>Cc:</b> dspace-general@mit.edu<br>
<b>Subject:</b> Re: [Dspace-general] Displaying forms according to content
type.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Well, let me group all the
information and conclusions we've got so far.<br>
<br>
Kim Shepherd has suggested SWORD as a way of creating alternatives submission
interfaces for the content type based submission process we want (this email
Kim sent me is attached in the end of this email). We think this is not exactly
what we need because we'd ought to have a form with all possibilities (the
fields, the attributes) of all content types and then, after the item has been
inserted, for example, the item's DB row would have blank fields. Therefore,
for us, SWORD is only useful for developing more agile submission apps, other
than the web-not-that-agile interface. Let me know, Kim, if our conclusion
about SWORD is not correct.<br>
<br>
Graham Triggs has said that it is not necessarily that hard to develop a form
selector based on content type and has given some instructions about how to do
it. After following his instructions and looking at Dspace classes we found
that we need to know more about Dspace's structure to feel able to change
anything without causing undesired side effects.<br>
<br>
Finally, our choice came from the experience told by Paulo Jobim: to create
collections related to the content type (books, articles, images, etc) and also
collections related to the item's classification (philosophy, sociology,
anthropology, etc...). So, we won't have to change the code and we're able to
create different forms for each collection, that is, different forms for
different content types, dealing with configurations Dspace already provides.
The problem is that the item will have to be mapped: after inserting it
according to its type, it must be mapped to its classification collection. Our
next step is to integrate item mapping into the submission process. Any idea?<br>
<br>
Thank you all for the contributions. <br>
<br>
***<br>
<br>
Kim's email about SWORD:<br>
<br>
<i>> Hi Yuri,<br>
><br>
> Perhaps SWORD can help -- there are Java and PHP libraries around.<br>
><br>
> I haven't implemented anything yet myself, but this is the path I'm taking<br>
> to build a submission interface that can handle different forms for<br>
> different resource types without creating extra clutter in the<br>
> collection/community hierarchy.<br>
><br>
> There is lots of cool stuff SWORD can do, but rather than list it all,
I'll<br>
> just give you some links: <a href="http://www.swordapp.org/">http://www.swordapp.org/</a>
and<br>
> <a href="http://www.ukoln.ac.uk/repositor">http://www.ukoln.ac.uk/repositor</a><<a
href="http://www.ukoln.ac.uk/repositories/digirep/index/SWORD">http://www.ukoln.ac.uk/repositories/digirep/index/SWORD</a>>For<br>
> sh <<a href="http://www.ukoln.ac.uk/repositories/digirep/index/SWORD">http://www.ukoln.ac.uk/repositories/digirep/index/SWORD</a>><br>
> ies/digirep/index/SWORD<<a
href="http://www.ukoln.ac.uk/repositories/digirep/index/SWORD">http://www.ukoln.ac.uk/repositories/digirep/index/SWORD</a>>
<br>
><br>
> There is a DSpace SWORD module since 1.4.2 (perhaps earlier?)<br>
><br>
> Cheers,<br>
><br>
> Kim<br>
></i><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Sat, Feb 21, 2009 at 6:21 AM, Graham Triggs <<a
href="mailto:graham@biomedcentral.com" target="_blank">graham@biomedcentral.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal>Actually, it isn't necessarily that hard (providing you are
using 1.5+, to accomodate altering the order of submission steps, and don't
mind the solution being a bit of a hack).<br>
<br>
The DCInputsReader that drives the metadata forms already has a form selector
based on the collection-handle.<br>
<br>
In an ideal world, you may extend the DCInputsReader to provide other selection
mechanisms - but you could just take the path of least resistance locally, and
simply change the describe step to pass any arbitrary data that you want in
place of the collection handle (for example the Mime type) when calling
DCInputsReader.getInputs().<br>
<br>
Then, in the input-forms.xml, you would have:<br>
<br>
<form-map><br>
<name-map collection-handle="default"
form-name="traditional" /><br>
<name-map collection-handle="audio/mpeg"
form-name="mp3" /><br>
</form-map><br>
<br>
<form-definitions><br>
<br>
<form name="traditional"><br>
<page number="1"><br>
...<br>
</page><br>
</form><br>
<br>
<form name="mp3"><br>
<page number="1"><br>
...<br>
</page><br>
</form><br>
<br>
G<o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<br>
On 13/02/2009 13:14, Yuri wrote:<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<div>
<p class=MsoNormal>Robin, I think we should have asked before trying to find a
way DSpace<br>
inside. =P<br>
Really thank you for your fast answer, Robin.<br>
<br>
Perhaps someone have tried a way of doing it. Anyone? (Even I ask, our<br>
conclusion is that developing this in DSpace is not that easy.)<br>
<br>
Yuri<br>
<br>
On Fri, Feb 13, 2009 at 10:43 AM, Robin Taylor <<a
href="mailto:robin.taylor@ed.ac.uk" target="_blank">robin.taylor@ed.ac.uk</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><mailto:<a href="mailto:robin.taylor@ed.ac.uk"
target="_blank">robin.taylor@ed.ac.uk</a>>> wrote:<br>
<br>
Hi Yuri,<br>
<br>
Unfortunately Dspace doesn't have a type based submission. The
best<br>
you can do is what you described, have different collections for<br>
different types. Sorry to not be of more help.<br>
<br>
Robin.<br>
<br>
Robin Taylor<br>
Main Library<br>
University of Edinburgh<br>
Tel. 0131 6515208<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:dspace-general-bounces@mit.edu"
target="_blank">dspace-general-bounces@mit.edu</a><br>
<mailto:<a href="mailto:dspace-general-bounces@mit.edu"
target="_blank">dspace-general-bounces@mit.edu</a>><br>
> [mailto:<a href="mailto:dspace-general-bounces@mit.edu"
target="_blank">dspace-general-bounces@mit.edu</a><br>
<mailto:<a href="mailto:dspace-general-bounces@mit.edu"
target="_blank">dspace-general-bounces@mit.edu</a>>] On Behalf Of Yuri<br>
> Sent: 13 February 2009 12:20<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> > To: <a
href="mailto:dspace-general@mit.edu" target="_blank">dspace-general@mit.edu</a>
<mailto:<a href="mailto:dspace-general@mit.edu" target="_blank">dspace-general@mit.edu</a>><br>
> Subject: [Dspace-general] Displaying forms according to
content type.<br>
><br>
> Hi everyone.<br>
><br>
> Let me introduce my self, once I'm new here and I don't know<br>
> how much formal people are here. ;-)<br>
><br>
> My name is Yuri Gomes Cardenas, I'm brazilian and study in a<o:p></o:p></p>
</div>
<p class=MsoNormal> > public university (<<a
href="http://www.ufsc.br" target="_blank">www.ufsc.br</a> <<a
href="http://www.ufsc.br" target="_blank">http://www.ufsc.br</a>>>) which
is<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
located in the<br>
> south, Florianópolis, Santa Catarina state. I work in a<br>
> informatics laboratory (where we use, develop and promote<br>
> free software) of the university and the project I'm engaged<br>
> now has to do with a digital library with which we aim to<br>
> give support to teachers of public high schools, of<br>
> philosophy and sociology disciplines. After some search and<br>
> attempts, we found DSpace and started learning how this<br>
> software works.<br>
><br>
> The question is:<br>
><br>
> Does anyone know if DSpace has some native mechanism for<br>
> displaying the submission forms according to the content<br>
> type? That is, once I choose a "audio" content
type, the next<br>
> steps should display some set of field (obviously, related
to<br>
> this content type) and if I choose an "article",
another set<br>
> of fields (not necessarily completely different) are<br>
> displayed. We already know that it's possible to change<br>
> forms' fields according to Collections, but we do not think<br>
> this would be the best way of doing that.<br>
><br>
> And I hope my bad written english do not interfere my<br>
> threads' understanding. =)<br>
><br>
> Thanks in advance.<br>
><br>
> Yuri Gomes Cardenas<br>
><br>
><br>
<br>
<br>
--<br>
The University of Edinburgh is a charitable body, registered in<br>
Scotland, with registration number SC005336.<br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal>------------------------------------------------------------------------<o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<br>
_______________________________________________<br>
Dspace-general mailing list<br>
<a href="mailto:Dspace-general@mit.edu" target="_blank">Dspace-general@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/dspace-general" target="_blank">http://mailman.mit.edu/mailman/listinfo/dspace-general</a><o:p></o:p></p>
</div>
</blockquote>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>