You can make your own custom vocabulary term to deal with your particular local needs. But you can also indicate through Semantic Web machinery that your vocabulary is a special case of an existing term. That way, you still have interoperability with the existing term.

For example, you may have a pressing need to differentiate in your context between Honours theses and Graduate theses. But you can also declare that both your “Honours theses” and “Graduate theses” are subclasses of Thesis as defined in Bibo (or whatever). So a system set up to deal with Bibo types can still deal with your localised subclasses. That kind of interoperability, we have not had with unstructured vocabulary lists.

“CAIRSS sites:if you have configured you repository…”

You might want to consider adding to the point on building a good site to specifically mention good use of markup, particularly with respect to headings and page titles. I would hope that most repository software do a reasonable job of this out of the box however it is also possible to regress if branding or other work is not done well.

Cheers
Mark

Thanks for the opportunity to have a look at this – I didn’t see any glaring errors or typos. But there was one thing – could you explain the following expression a little? It is not clear to me:

“if, for example, you have made very zealous use of handles and try to reference a datastream via a handle or DOI then Google Scholar may not index it.”

We use handles, but I don’t know if we ‘reference a datastream via a handle’. I know that our technical person was encouraging us to use the handle rather than the url that has the word ‘dspace’ in it – is this a problem or am I reading the terminology in the guide wrong?

That statement might need more teasing out in the guide.

Danny