Page History

...

1. From Anja Le Blanc: REST API updates
   1. I already got a pull request (DS-1854 / PR#434) for improving the search capabilities and adding the context to the search results.
      At the moment I am working on (well, nearly finished) adding the request for stats histograms to the API.  e.g.
      
      1. http://dspace.jorum.ac.uk/rest/items/10949/16838/stats?start=2013-01-01&end=2015-01-01&interval=month 
      2. http://dspace.jorum.ac.uk/rest/items/10949/16838/stats/view?start=2013-01-01&end=2015-01-01&interval=month 
      3. http://dspace.jorum.ac.uk/rest/items/10949/16838/stats/download?start=2013-01-01&end=2015-01-01&interval=day 
   2. I still want to implement the same for any search results, so that API users can request things like usage data for their institution, or for their subset of items. 
2. From Anja Le Blanc: Stats recording 
   1. I have not done anything about this point, but I would like to see an additional field in each stats record which indicates the component from which the view/download was generated. I would like to see how much traffic is coming in via the XMLUI/REST and possibly adding some stats for OAI harvesting requests.
3. From Jeb Schiefer: Embargo support on commandline
   1. My name is Jeb Schiefer. I am an undergraduate at Virginia Tech. This semester I have been enhancing DSpace for the Virginia Tech library (http://vtechworks.lib.vt.edu/). I have been working with another student - Paul Sharma.
   2. We were asked to add embargo support to the item import command line tool. We have forked the DSpace project at https://github.com/jebschiefer/DSpace and are working out of the "cli-embargo-4_x" branch. You will notice that we are currently targeting the DSpace 4.0 because Virginia Tech will be updating to that version in the future. Some of the code we've written isn't done "the DSpace way" in order to accommodate some requirements of our semester project, however, we can refactor to code in order to be accepted in to DSpace 5.0 if that is a feature you agree should be added.
4. If you have a feature Idea or code that you wish to add to the discussion, either add it to this list or email Tim Donohue 
   1. Please provide a general overview of the use cases or needs which you are trying to meet
   2. Please also provide any relevant links to JIRA ticket(s) or code or mailing list discussions, etc.
   3. PLEASE NOTE: While we will attempt to discuss every item in this list, our meeting usually only lasts approximately one hour. If we are unable to discuss your topic, we will reschedule it for the following week.

...