Digital Content Manager

1. Digital Content Manager Antti Moilanen, Kinoshita Lab anttimo@ka.riec.tohoku.ac.jp

2. Outline • Introduction • Example problem case • Proposed solution • Construction • Example walkthrough • Summary and future work

3. 1 Introduction Research plan: • To implement system that helps user to manage digital content Motivation: • Amount of digital content we have to work with is growing everyday • This also means that problems we are having managing it are coming more meaningful and important

4. 2 Example problem case Storing the file: • User has article Sendai.doc he wrote while being exchange student in Japan. • He has two possible folders to select from: • Articles • Japan • How to decide where to store the file? Sendai.doc ? Articles ? Japan

5. 2 Example problem case Searching the file: • User decided to save the file to article folder. • Afterwards he thinks it’s in Japan folder but he finds out it isn’t. • How to avoid this problem?

6. 2 Example problem case We have two main problems: • Deciding where to store a file • How to find the file we are looking for, especially if we already had problem deciding where to save it

7. 2 Example problem case Conclusion: • To solve mentioned problems, we need system that’s able to: • Decide or help user to decide where to store files • Make finding files easier

8. 3 Proposed solution Storing file: • Instead of deciding place where to store a file, user gives system keywords that are related to the file • Beside keywords also file-type affects to the saving location • System saves the file and creates metadata which has keywords and information about location of the file Agent System Checks file-type Keywords: Japan Article Checks keywords Sendai.doc Saves file Informs user

9. 3 Proposed solution Searching files • User gives keywords related to the file he wants to find • Using keywords system searches and gives user files that matched these keywords Agent System Keywords: Japan Article Takes keywords Searches files Sendai.doc

10. 4 Construction System has two different main parts • Graphical User Interface • Agent system • Agent System • Functions to communicate with GUI • Functions decide where to store files using user input • Functions to find files using user input GUI • Functions to receive user input (file and keywords) • Functions to show feedback from agent system

11. Category-agent Category-agent Category-agent Category-agent 4 Construction Agent-system: • Based on needed functions agent system is created using three different kind of agents: • UI-agent • Category-agents • Manager-agent Agent System Manager-agent UI-agent GUI

12. 4 Construction UI-agent • Operates the User Interface i.e. it has base process which creates the graphical user-interface • Has functions to handle messaging between GUI and agent-system

13. 4 Construction Category-agent • There is multiple amount of category-agents and each of them has set file-types and keywords • Using these it’s accepting or denying files user wants to store • If the file is suitable it makes file-entry which has name of the file and keywords user gave for that file • When searching it’s comparing given keywords to keywords in the file-entries

14. 4 Construction Manager-agent • Manager-agent is working between two previously mentioned UI- and Category-agents • Broadcasting requests got from UI-agent to categories • Sums up results got when storing or searching file and sends them to UI-agent

15. 4 Construction Graphical User Interface • GUI is handling communication between user and system: • Providing user input to system • The file user wants to store • Keywords to be attached to this file • Keywords used when searching for a file • Providing feedback from system to user • Did storing or searching succeed or not? • If it didn’t, what went wrong?

16. 5 Example walkthrough Information about current implementation • Current implementation isn’t yet really saving real files. It’s saving file-entry with filename and keywords into category agent’s working memory • It still enables way to test agents and see if they are working

17. photos Keywords: sendai, report File-types: gif, jpg documents Keywords: article, report File-types: doc, txt 5 Example walkthrough • File user wants to store: • Sendai.doc • Keywords user sets for this file: • report • article • Current implementation has two category agents:

18. Storing the file GUI UI Manager _broadcast Documents Photos User- input file :name Sendai :type doc :keywordList (report article) Request-information file :name Sendai :type doc :keywordList (report article) Request-information file :type doc :keywordList (report article) Deny Deny saveStatus :category photos :status "filetype not suitable" saveStatus :category photos :status "filetype not suitable" Inform Inform Category photos: filetype not suitable fileType :suitability OK Store-file file :name Sendai :type doc :keywordList (report article) Inform Inform File :status saved :category documents File :status saved :category documents Inform File sendai.doc was saved successfully into documents category!

19. Searching the file GUI UI Manager _broadcast Documents Photos User- input keywordList :list (report article) Request-information keywordList :list (report article) Request-file keywordList (report article) Inform Search :status found :category documents :list ((searchResult :list Sendai :type doc)) Inform Search :status found :category documents :list ((searchResult :list Sendai :type doc)) Inform File found from documents category

20. 6 Summary and future work • Summary: • Current simple implementation works, but should be tested with more categories and file-entries • Future work: • More categories • File browser to GUI so user can actually select a real file he wants to save • Database where files are stored • More options to searching files • File-types • Operators like AND, OR etc. • GUI with better looks and usability • Evaluation of the system by comparing it to same kind of already existing systems