Working with Google on this, they were mostly happy with us getting 80%
complete, with 20% effort, and in these complex cases (where PDF is just a
supplementary dataset), to just punt.
Locally, we've added an additional rule, that the PDF be readable by the
anonymous user. We will sometimes suppress a PDF whenever a rights issue
crops up, or to allow us to psuedo-version, and add an additional version.
https://github.com/osulibraries/DSpace/commit/ff3ef1b0f6cc906e42b0e22d04d52f9a98c9742e
Perhaps this is the start of tackling the remaining 20%, where sites with
more complex bitstream setups would either hard-code their modifications,
or if desired, build a configurable strategy. Thats why the method was
called getPDFSimpleURL, as opposed to getPDF_MIT_URL.
In our situation, I think that if there is a PDF present in an Item, its
usually the most important file.
Peter Dietz
On Mon, Jan 14, 2013 at 8:56 AM, helix84 <[email protected]> wrote:
> 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
>
------------------------------------------------------------------------------
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
