 So, good afternoon everybody. I am Pankaj Patil. I am coordinating the efforts in the development of OER repository. In today's discussion we will see what is OER, what is OER repository, why we want to make it, what are the features of the OER, architecture of the OER etc. So, these are the contents. So, do you know what is OER? Anybody know? Have you used MIT OCW? Open courseware? Yeah, but what does it mean? So, it means resources which are available for the open field. Okay. Just pre or something more than that. Okay, anyway. So, OER means open educational resources. So, any educational material which is in a public domain is called as OER. Okay. So, what is, what does mean by public domain? I will come to it later. We will understand educational materials. So, educational materials can be of any type, like digital and non-digital. In our OER repository we will be dealing with digital material. Okay. So, digital material means say video lectures, audio lectures or PDF files, images, animations or software. Anything which is in a digital form, educational material is OER for us. Now, who are the users of the OER? Broadly, any learner is a user of the OER. So, students, learners, professionals, teachers and researchers. Now, I said anything which is in a public domain is called as OER. Okay. So, public domain means what? So, if you consider any product, let it be software, hardware or educational material, it is released with some license. Okay. So, the material, educational material which is released with say CCBYSA license is OER. CCBYSA means CC means Creative Commons license, BY by attribution and SA share alike. So, this OER will be released with CCBYSA license. This CCBYSA license will empower user to use these OERs with these 5R characteristics. 5R means retain, reuse, revise, remix and redistribute. Now, one friend told like OER means free. So, it's not only free, it is something beyond that and that is 5R. Okay. You can take resource, you can revise it, remix, reuse, redistribute. Okay. So, that's all about OER. Now, OER repository. So, our goal is to develop a digital repository of OER. Now, why we want to develop this OER repository? So, to expand access to learning, encourage to modify and enhance course materials, rapidly disseminate information and save heavy cost of education. For developing OER repository, we'll be using this space software. So, this space is an institutional repository system which is developed by HP Lab and MIT. So, this is one of the most popular repository system which is used for harvesting content. Now, we'll be using Java Enterprise Edition, Spring Framework, ELK stack, that is Elasticsearch, Logstash and Kibana, Ajax JavaScript and Frontend Technologies, HTML, CSS Bootstrap. OER repository information architecture. Now, in our OER repository, we'll be releasing around 12,000 plus video lectures and almost same number of PDF files. Okay. So, now these lectures are organized in different courses, subjects and domains. Okay. So, this diagram represents the information architecture of the OER repository. Domain. Domain means a branch. Okay. Like engineering is a branch or say arts, science, medical, etc., these are the domains. Then subject. Okay. So, if you consider programming as one subject, then inside that there will be courses and inside course there will be OER. OER means it can be video, audio, image or PDF. Each OER will be associated with metadata. Okay. Do you know metadata? Information about? Data about data. Yeah, that is the definition. Have you uploaded videos in YouTube? Okay. You might have or may not, whatever. So, when you upload video in YouTube, you just don't upload video. Along with video, you fill some form. Okay. That consists of fills like name of the video, creator, licenses, keywords, etc., etc. So, this extra information which is information about that specific digital asset. So, this information is metadata. Okay. So, in our OER repository, we will have metadata for every digital asset or every each OER. Okay. So, this diagram also represents like the authority of the users. Okay. Domain. Domain will be managed by application administrator. Subjects will be managed by subject admin, course by course admin. And OER, while uploading these OERs in the OER repository, it will pass through some workflow. Okay. And in this workflow, there will be different users like curator will be there who will submit OER, means upload file along with metadata. Then, after submitting this OER, it will pass to reviewer. Reviewer will review metadata. And once he will approve, it will be publicly available. Now, learner. Learner can access any content he can download or he can do lot of stuff. We will see it. OER repository system architecture. So, basically, we will be developing this OER repository on top of this space. This space will be like main engine on top of which we will be developing this OER repository. So, this is an architecture diagram of this space. So, as you can see here, this space is developed using MEC design pattern. So, I will just briefly describe this. So, at bottom, it has storage layer. Now, in OER repository, there will be two types of storage. One, actual file storage. That means video, document, image, etc. That is file storage. And whatever metadata is there associated with that digital asset, it will be stored in a database, post-grace SQL. So, in storage layer, it is a file storage as well as database. On top of storage layer, there is a business logic layer. This business logic layer is having different components, which is basically for managing content, managing users, workflow, authorization, etc. Then, application layer. Now, application layer is like interface for external applications. This space is one application. This space will interact with other applications. So, this application layer is interface for other applications to communicate with this space. For example, web UI. Though it is an actual part of OER repository, means user interface. Though it is a part of OER repository, it will be considered as an external. So, this application layer will provide a facility to develop this user interface. Similarly, statistic tools. So, in technology, I spoke about ELK stack, Elasticsearch, Kibana and LogStage. So, we will use this statistic tools application layer for extending visualization of usage of the OERs. Then, there are other application layer components like OII-PIMH, open archives initiative protocol for metadata handling, simple import-export, METS-export and media filter. Most of the things like OII-PIMH, simple exporter-importer and METS-exporters, these are for importing or exporting digital assets with other applications. Features of the OER repository. Already we have covered this briefly. There will be basically six types of users, admin, subject admin, course admin, curator, reviewer and learner. What they can do is mention as the authority. Like admin will be responsible for managing domains, subject admin for subjects, course admin for courses. And curator, reviewer and learner, they will have access of OERs, means digital assets and metadata. Curator, reviewer and learner, they don't have access to courses. They have access to only digital assets and metadata. We will have mechanism where these all roles, user roles will have facility to do crowd operations, means create, read, update and delete. For example, admin will be able to create, read, update and delete domains, likewise. Other features, discovery. In discovery we will have two types of discovery. One is browsing and other is search. Can anybody tell what is the difference between browse and search? Or both same? Can anybody tell what is browsing and what is searching? So browse means we will not search any asset, digital asset with keyword. System will list the domains, subjects, courses and OERs. If you will click on some domain, whatever subjects are under that domain, system will list. If you will click on some subject, system will list courses. So this is a very conventional way of navigating through any application. So we will have this feature, browsing, browsing through all courses. Other feature will be search. Now search is with keyword search. Now as I mentioned, every OER or digital asset will have associated metadata for that. Now do you know how actually search happens? Like in YouTube you enter some keyword. How system returns different videos? How actually system returns videos? Which information is responsible for this searching mechanism? What is the role of metadata? When we upload videos in YouTube, why to insert metadata? I can simply upload video also. So that when user searches for particular thing, we can search for that keyword in the metadata. And the video which is most suited search according to that particular search, we will show that video in that relevance. I will give you simple example. You create different types of documents or files in your computer. You give some name to that. Select test document, test.docx. So this name of the file, this test, what is this? It's a metadata. Now you give this name. When you right click on any file and you look in properties, system displays more information. Date of creation, date of modification, ownership and also size etc. format. So all this information is metadata in our file system. Similarly in OER repository, every digital asset or any OER will have metadata. Metadata will be Dublin core and IEEE LOM. There are different metadata standards which are widely accepted worldwide. Dublin core and IEEE LOM will be using it. So whatever metadata we will inject due to that system will return results. If I will enter some keyword, then if I will press search button, then system will search for files which are having that keyword in a metadata. And those results will be displayed. So in this core you will have browse and search. Also you will have faceted search. Faceted search means you use different e-commerce portals. And you search for some product and system displays lot of results. To narrow down search results you apply different filters like price range, rating, popularity, reliance etc. So we will have similar filters here. Display OER. Now as I mentioned our OERs will be of video, PDF, image etc. So we will have mechanism to display these OERs in the browser. OER download will facilitate users to download the OER. At the same time we will keep log of the users who have downloaded files etc. Rating system will build a mechanism where user will be able to provide rating on some scale say like 1 to 5 or 1 to 10. For every OER or course or subject, OER dashboard, users will have their own dashboard. After signing in user will be redirected to page where they will find dashboard. In a dashboard they will find courses where they have registered. Also they will find the materials which they have downloaded. So likewise dashboard will be there. Also there will be a course custom playlist. I will come to custom playlist later. Statistics will be logging in information very heavily. Each and every activity of the user will be logging in. And based on these logs will create different statistics. Consider single OER. If you consider single OER will produce statistics or will graphically display the usage pattern. Like today how many users viewed this OER or monthly how many users viewed downloaded etc. Custom playlist. Now there will be multiple courses for same course. If you consider C programming language there will be different courses for C programming. Now it is very natural that some content from some X course will be better than some content in Y course. Now as an end user I may be interested in content from different courses. So we will provide mechanism for users where they will be able to create custom playlist where they can add different OERs in the playlist and they can create their own course. Definitely that will be accessible for them only. That playlist won't be accessible for any other user. So these are the very big features and also I have described very high level architecture of the diagram OER repository. Any doubts? So this project will be for 6 weeks and it is extremely challenging project. As I mentioned it will be built on top of this space which is written in Java Spring framework which is extremely challenging. We have seen like to modify some feature of this space it takes lot of time. Like to implement single feature of this OER repository you may need to write just 10 lines of code but to write that 10 lines of code it may take one week. So it is extremely challenging project. Thank you.