asaworker
asked on
How do you pull an external farms document list into another farms repository using SharePoint 2007 MOSS
We need the ability to pull the contents of an external Sharepoint farms document list into another farms repository. We want to display the external farm list in the design of the other farms template. Both farms live on the same server. One is public...the other one is private. Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
if the source list changes..do you have to do this process again...or does this create the link going forward.
ASKER
awesome
ASKER
I got some feedback...Here is what our business units want:
They want the private site to be the “single source of information” for approved data definitions. They want the public site to be able to view it (and not have to copy the documents from one library to another on an ongoing basis), since they are constantly adding documents to the private site, and don’t want to have to load them in two places.
Does your solution fix this problem?
They want the private site to be the “single source of information” for approved data definitions. They want the public site to be able to view it (and not have to copy the documents from one library to another on an ongoing basis), since they are constantly adding documents to the private site, and don’t want to have to load them in two places.
Does your solution fix this problem?
If the list definition changes, yes, the target one must also. You get a fairly obvious error message but you can save lists as templates and export them.
If the flow of information is one-way, yes it solves the problem, however, if it list items need to be updates both ways, I would consider setting up a single site collection with the correct permissions et up to allow public users the desired level of access.
If you can provide a bit more of a detailed explaination of what you're trying to achieve then I can try and point you in the correct direction.
If the flow of information is one-way, yes it solves the problem, however, if it list items need to be updates both ways, I would consider setting up a single site collection with the correct permissions et up to allow public users the desired level of access.
If you can provide a bit more of a detailed explaination of what you're trying to achieve then I can try and point you in the correct direction.
ASKER
They want to have a single place on the private site where they create their information that is shared with the public site. When it is displayed on the public site, it needs to use the theme of the public site...not the private site.
I see - so since the flow of information is one-way, you can use the method I have suggested already to move the data once it is ready. There are alternatives but it sounds like you have two site collections setup already?
You could have separate sub-sites (with different themes) and then use workflows to move/copy list items or use webparts/dataviews to roll up the list items. This would only work between sub-sites on the same site collection though.
You could have separate sub-sites (with different themes) and then use workflows to move/copy list items or use webparts/dataviews to roll up the list items. This would only work between sub-sites on the same site collection though.
ASKER
Is there a way that the content automatically get updated on the public site when the private site is updated? I can convice them to do it once...but have it run automatically when the private site gets updated...does your method handle this?
The method I gave you (which you accepted as the answer) would require that you put the commands that run the export/import into a batch file and then you can use scheduled tasks on the sharepoint server - Start > All Programs >Scheduled Tasks I think - to automatically update the public site on your pre-defined schedule depending on how current you need the public site to be.
ASKER