I am curious about what strategies people use on where to store files
(such as XSLTs) that are used by their disseminations.

>From what I have seen, creating separate fedora objects for storing them
which is one method used, especially if the XSLT might be used by multiple
SDeps or Content Models. In this strategy, would standard practice be to
store all the files for a specific SDep in a single FDO or give each their
own FDO?  

If specific XSLTs are only used by a specific Content Model or SDep, is
there any issue with storing it in the SDep object itself?  It seems like
a logical place to store files used by the deployment without requiring a
separate object(s), but maybe there are performance, logistical or common
fedora practices that suggest against this.

I've tried both methods and both work.  I'm just not sure if there is a
reason to prefer one over the other.

Any input or commentary is appreciated.


-- Jon Gibson, Software Developer
-- University of Texas Libraries




------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to