On 19 June 2015 at 08:47, Monika C. Mevenkamp <moni...@princeton.edu> wrote:
> The reason Anurag gave for disliking cover pages was, that they can make > it difficult to discern things like - author - title, journal, …. It seems > to me that if the generated cover page includes those metadata fields along > with custom text explaining the origin of the pdf, google scholar should > not have any difficulty getting to the metadata they are looking for. > Another ‘bad case’ Anurag mentioned was documents that have multiple cover > pages. I expect that the current implementation does avoid adding cover > pages to already ‘covered’ pdfs. > > Monika > Yes, one of my immediate thoughts was: is that a fundamental problem with cover pages, or is it possible to "Do It Right"? If we inject good metadata into the derived PDFs and ensure that titles, author, date were all high up on page one, could we actually be helping to an extent? I hadn't thought of the 'cloaking issue' though. If low entropy between page 1 of repository PDFs would cause Google to penalise us, then that's hard to get around without finding a way to not serve them the cover pages. Cheers Kim M: k...@shepherd.nz T: @kimshepherd P: +6421883635 0CCB D957 0C35 F5C1 497E CDCF FC4B ABA3 2A1A FAEC https://keybase.io/kshepherd
------------------------------------------------------------------------------
_______________________________________________ Dspace-general mailing list Dspace-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-general
