[5:56] where we should implement these kind of functionalities? in the UI or in the REST API?

Art Lowel [5:57 PM] I’ll have to do some reading first, I hadn’t heard of that

Andrea Bollini [5:58 PM] essentially it requires that when you serve an item page you add some HTTP header to link to specific content in the page

[5:58] the URL of the author (on ORCID), the URL to download the bitstreams

[5:59] it is useful to provide an easy path for harvester to access your repository without the need to parse the html

Art Lowel [5:59 PM] So that’s quite similar to what we’re doing for google scholar then?

Andrea Bollini [5:59 PM] yes but as HTTP Header insted of metatags

Art Lowel [5:59 PM] I see

Andrea Bollini [6:00 PM] but also google scholar is a good example of my concerns

[6:00] where we should implement the functionality?

Art Lowel [6:00 PM] I had also assumed that that would be the UI

Andrea Bollini [6:01 PM] I have just realized that the UI is more than a view layer on top of the REST API

[6:02] not necessary a bad thing... just it wasn't evident to me

Art Lowel [6:02 PM] I think it could be, but then the Rest API would have to become very large and contain lots of redundant ways to show the same info, and I don’t think that would be a good thing

Andrea Bollini [6:04 PM] ok... as said I just need to think on that from a different perspective but it is something that we should keep in mind. It will be useful to repost similar question on each feature that is "borderline"

Art Lowel [6:04 PM] I agree

Andrea Bollini [6:05 PM] ok, we are out our meeting time. Are there anything else that you want to discuss?

Art Lowel [6:05 PM] not at the moment

Andrea Bollini [6:06 PM] I guess that we can close the meeting. See all of you on hangout next week