On Mon, Jan 14, 2013 at 2:43 PM, Richard Rodgers <[email protected]> wrote: > In those cases the rule you propose would ask > GS to index the wrong bitstream.
Hi Richard, I didn't see that Andrea proposed anything yet, so I think you're referring to mu proposal. Also, thank you for sheding more light on the reasons behind status quo. > * should there be a site-wide mapping rule, or one per collection (per > format type, etc)? > * probably should be be a default (maybe just the current hard-coded one) - > so that we don't force additional configuration > * how should the rule be expressed? > * how to limit runtime penalties What about adding another bitstream table column (according to what you said, primary bitstream may not adequately express this intent) or Solr index field? It would allow the users complete flexibility in redefining any default rules we cast upon them (we could provide some curation tasks with different rulesets to do that) and by not evaluating the rule at browse time it would avoid any runtime penalty. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
