We have several disseminations of our objects which are all made by xslt's (the Saxon service). All the xslt's are datastreams of one special "xslt object". Putting all the xslt's together is especially handy when you have many xslt's and some of them are imporiting each other. Otherwise you could jus as well add an xslt datastream to the service deployment object. The special object is referenced in the service deployment object that takes care of the dissemination. That is done in the DSINPUTSPEC datastream where you have a fbs:DSInput element for the xslt which can carry a pid attribute if the xslt is a datastream of another object. So the only thing the data objects need is "hasModel" link to the right content model and the CMA does the rest.
Egbert Gramsbergen TU Delft Library, Innovation / 3TU Datacentrum http://data.3tu.nl _______________ Van: Scott Prater [pra...@wisc.edu] Verzonden: vrijdag 1 februari 2013 3:35 To: Support and info exchange list for Fedora users. Onderwerp: Re: [fcrepo-user] Digital Object Reuse in Service Deployment Hello, Ryan -- We're doing something similar in our setup. We create digital objects that contain a XSLT datastream, and then link the xml *object* to be transformed to the XSLT *object* (not XSLT datastream) in the xml object's RELS-EXT. We have a disseminator that links to a webservice which reads the RELS-EXT, retrieves the XSLT datatstream, and does the transform. It's been some years since I set it up, so I may not have the details right. Let me know if you'd like more info. -- Scott On 01/31/13, Ryan Ward wrote: > > > We have a large number of items in our repository that all need a common XSL > applied to them for certain kind of display. In the demo objects, there is > something similar to what I am trying to create. In that case, there is a > digital object which contains both the datastream to be transformed and the > xlst as datastreams. > > This seems excessive to me when I will have potentially tens of thousands of > objects that could all use the same xslt. I have a couple of approaches in > mind, but I am not sure what would work. I wanted to define the xslt as a > datastream in an object of its own, then point a datasream on each object to > this one object's datastream. However, if I use the internal uri > (info:fedora/foo:001/bazDatastream) it throws an error. I can use the URL > reference to the datastream and get that to work > (http://hostname/fedora/objects/foo:001/datastreams/bazDatastream/content). > This just struck me as poor practice potentially. I did not know if there was > a better way to link to a datastream of another object. > > > Alternatively, I thought maybe I could define a relationship to the > datastream in RELS-EXT and then pull that datastream out as a parameter in > the sDep. However, I cannot find any good info on if the is possible or how > to accomplish that. So I am wondering if there are any good resources besides > the base documentation on creating service deployments. I haven't found much > in my Googling. > > Ryan Ward -- -- Scott Prater Library, Instructional, and Research Applications (LIRA) Division of Information Technology (DoIT) University of Wisconsin - Madison pra...@wisc.edu ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
