I think I would persevere with making a variation on the 'Link to a Document'
Content Type.
If you take a site template, and import it into studio, you can see exactly how
the 'Link to a Document' content type works and what the columns are etc. and
more importantly how it links to the NewLink.aspx form.
Perhaps make your own content type similar to this, targeting your own ASPX
form deployed into the LAYOUTS directory. You may need to build a custom field
with underlying type of URL that accepts the DocID and stores the link to
render in list view.
Cheers,
J.
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/";>
<ContentType ID="0x01010A" Name="Link to a Document"
Group="Document Content Types" Description="Create a link to a document in a
different location." Overwrite="TRUE"
FeatureId="{695b6570-a48b-4a8e-8ea5-26ea7fc1d162}"
xmlns="http://schemas.microsoft.com/sharepoint/";>
<Folder TargetName="_cts/Link to a Document" />
<FieldRefs>
<FieldRef
ID="{c042a256-787d-4a6f-8a8a-cf6ab767f12d}" Name="ContentType" />
<FieldRef
ID="{5f47e085-2150-41dc-b661-442f3027f552}" Name="SelectFilename" />
<FieldRef
ID="{8553196d-ec8d-4564-9861-3dbe931050c8}" Name="FileLeafRef" Required="TRUE"
/>
<FieldRef
ID="{8c06beca-0777-48f7-91c7-6da68bc07b69}" Name="Created" Hidden="TRUE" />
<FieldRef
ID="{28cf69c5-fa48-462a-b5cd-27b6f9d2bd5f}" Name="Modified" Hidden="TRUE" />
<FieldRef
ID="{822c78e3-1ea9-4943-b449-57863ad33ca9}" Name="Modified_x0020_By"
Hidden="FALSE" />
<FieldRef
ID="{4dd7e525-8d6b-4cb4-9d3e-44ee25f973eb}" Name="Created_x0020_By"
Hidden="FALSE" />
<FieldRef
ID="{c29e077d-f466-4d8e-8bbe-72b66c5f205c}" Name="URL" Required="TRUE" />
</FieldRefs>
<DocumentTemplate
TargetName="/_layouts/NewLink.aspx" />
<XmlDocuments>
<XmlDocument
NamespaceURI="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms";>
<FormTemplates
xmlns="http://schemas.microsoft.com/sharepoint/v3/contenttype/forms";>
<Display>DocumentLibraryForm</Display>
<Edit>DocumentLibraryForm</Edit>
<New>DocumentLibraryForm</New>
</FormTemplates>
</XmlDocument>
</XmlDocuments>
</ContentType>
</Elements>
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Maxine Harwood
Sent: Wednesday, 30 March 2011 7:00 PM
To: ozMOSS
Subject: how would you implement this?
My client has a document library in use with multiple content types. I've been
asked to add a facility where some documents (a new content type) can be linked
in the library rather than uploaded. Easy!
But, the link is not one the user can browse to. It's a link within another
application .e.g.: http://AThirdPartyApp/getDocument.aspx?docID=1234.
The "docID" is easy for the end user to find.
Ideally, I would like to prompt the user to enter the meta data and the DocID,
then generate the URL based on the information given, but the default
_NewLink.aspx prompts for the document link first?
So... with a dozen different ideas going through my head, I'm wondering how the
group would implement this?
It seems I can't simply a new form for a document library in SPD (SPD isn't
giving me an option for a NEW form in this document library).
I could build my own completely custom form for adding the data, and add this
to the ribbon? I think this is the best solution, but also the most time
consuming. Before I started coding, I thought I would see what other
suggestions might be around?
Another option could be to modify the _layouts/NewLink.aspx but I am reluctant
to modify OOTB pages unless there is no better alternative?
Is there a better or more efficient way?
_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
