 I am Pankaj Patil. I am working on a NULI project. OER repository is one of the components of the NULI project. We have started development of OER repository from last one year and we have achieved few of the things. So in this year internship, we are planning to do more on the repository. So we will start with this. So basically what is OER? So OER is like open educational resource. These open educational resources, these are the openly shareable, freely accessible and openly licensed educational content. It can be in the form of video, audio, document, image, anything or it can be simulation or any educational material which is under the open license can be considered as OER. So basically whatever OERs we do have, we have planned to release it with license CC BYSA. That is CC means Creative Commons BY that is a by attribution and SA that is share alike. These are open source licenses. This OER repository project is activities under OER repository project. We can divide in two major categories. One is software development part that is application development and other is metadata tagging of OERs. Just in a previous presentation, Nitin explained about the metadata. So what is the need of metadata? So consider like there is an application in which we want to inject OERs. OERs means any document, video or any educational material. Merely injecting educational content or OER doesn't make sense. If you simply upload video or share like scanned document of book. So for a user, it won't be searchable. To make it searchable or to apply say faceted searches on these contents, we need to tag them. So tagging is one of the critical activity. There are many challenges also in this tagging activity as explained by Nitin in previous presentation. It varies from human to human. Like if I will consider one video, then from my perspective there may be some keywords. By somebody else's perspective there may be few other keywords. So there is a team which is working on this metadata tagging activity. As a software developer, you don't need to care about that. There are different metadata standards available for tagging. For this OER repository, we are following Dublin core metadata standard and IEEE LOM. That is LOM means Learning Object Metadata. So this is like data handling part. In application development, we are using this space as a base software for this OER repository. This space is an institutional repository system which is developed at MIT, USA. We are using this space 6.2. This space is built on Java, Spring Framework, PostgreSQL. In this space there are two user interfaces available. One is JSP based and other is XML based. Currently, we are using JSP UI because it is responsible. Currently, I will just brief upon what are the currently implemented features of the OER repository. Currently, as administrator of the application can upload content in the repository along with metadata. Then this uploaded content gets published. Users of the website, that's anonymous user, can search content or browse content using faceted search. User can view content, whether it's a PDF or video. It opens in the disk space itself and user can download the content. These are the already implemented features. Now for this summer internship, we plan this following work. User profile and dashboard. Currently, learner role is anonymous user in the system. So we would like to make it authenticated user. There are advantages of doing that. Authenticated learner will be able to add courses in the personal dashboard. He will be able to get the list of resources which he has accessed already, list of downloaded files. Or as a learner, he will be able to comment on the different OERs. This rated content will be again used for searching. User will be able to sort content based on the rating. Next is recommendation system. This OER repository will have huge number of OERs. In the first page, there may be more than 10,000 OERs in the form of PDF and videos. So searching the right OER may be challenging. As a user, I would like to get some recommendations from the system. So we have planned to implement this recommendation system. This system will suggest users these are the recommended OERs for you. So this will do based on the previous search history of the user, or based on the search history from specific IP address. Next is field view and document streaming. Currently document and video, these are filled in the JSP page itself. If the document or video is very huge in size, then there may be a chance of getting buffering. So we have planned to host these documents and video on streaming server, maybe RAID5 streaming server for video and for document, something else. So basically we would like to display at a time one page instead of loading full document, at a time one page we would like to stream in case of document and in case of video may be this RAID5 streaming server. So this will reduce network traffic and it will give better user experience. So that's all the plan work for OER repository enhancement. Thank you. If you have any doubts, you can contact me.