ASKOSI

Software

Christophe Dupriez — 2012-01-27T12:01:00Z

Christophe Dupriez changed this page on Fri Jan 27 13:01:00 CET 2012:

!!! Software for Simple Knowledge Organisation Systems
!! Main use cases
* __creation__: top~-down and/or bottom~-up collection of concepts with their labels and translations;
* __organisation__: linking concepts together (hierarchies, related) and linking concepts and data (indexing);
* __distribution__: push/pull the Knowledge Organisation System to/by the applications and their users;
* __search__: by words, along links;
* __applications__: using the information is more and more "social": users may enrich the original knowledge and track how evolutions are accepted by the community.
!! Applications:
! [DSpace|http://www.dspace.org]
! [JSPWiki|http://incubator.apache.org/jspwiki/]
! [GraphViz|http://www.graphviz.org]

A fantastic drawing software~! Now integrated in ASKOSI...
! [Jaxe|http://jaxe.sourceforge.net/]
* [ConceptScheme XSD|http://www.askosi.org/ConceptScheme.xsd]
* [Jaxe Layout for ConceptScheme]
! [Protégé|http://protege.stanford.edu/]
! [RDF Browser|http://graphite.ecs.soton.ac.uk/browser/] : Quick and Dirty RDF browser by University of Southampton
!! Java modules:
! JAXB

Direct XML marshalling and unmarshalling of ConceptScheme and Concept classes ([ConceptScheme XSD|http://www.askosi.org/ConceptScheme.xsd]).
!
[Apache Cayenne|http://cayenne.apache.org]

Integrating SQL Databases and Java development.
! [Apache Click|http://click.apache.org]

Well structured development of efficient Web applications.
! Jersey (JSR 311):

REST Interface for Create/Retrieve/Update/Delete of concepts and concepts maintenance workflow.
! OpenRDF Sesame and AliBaba:
* We use their SparQL client
* Following this [article|http://www.devx.com/semantic/Article/37774/1954], Sesame can store information about RDF Statements and be used to query about meta~-metadata: information about UPDATING RDF statements (or SKOS statements).
! Simile Exhibit

Following this [message|http://groups.google.com/group/simile-widgets/browse_thread/thread/f81eb5f0b363e106/d355240121660fda?pli=1] it is interesting to see how to parameterize SIMILE to browse SKOS/RDF files
! [Crawler4J|http://code.google.com/p/crawler4j/]

It may be interesting to crawl specific websites and record which Concepts are referred by which pages and make this accessible in ASKOSI Concept usage displays. A Thesaurus driven index of specific sites...

ASKOSI story

Christophe Dupriez — 2012-01-27T11:41:12Z

Christophe Dupriez changed this page on Fri Jan 27 12:41:12 CET 2012:

!!! A possible~~Story~~>> <<story forof >> a project using ASKOSI

<<(''%%( background-color: rgb(175, 238, 238); )current developments%%'')

>>[{TableOfContents}]
!!! CoP initiative

A Community of Practice wants to integrate the knowledge and the services proposed by the different applications published by participating institutions.

One of the best way to get people to work together is to invite them:
# to make an inventory of their main sources of reference information,
# to define the concepts they will share.

ASKOSI accesses the information where it is:
# catalogs of concepts (with their terminology) are accessed where they are published, whatever they propose:
## SQL or SparQL servers
## RDF, XML or CSV files
# documents or operational information in different applications are accessed using URLs:
## concepts can be searched and results~' sizes are stored by ASKOSI;
## users~' search equations are stored in an history file, they can be tagged and reused;
## users~' accesses to individual documents or information are also recorded: they can be tagged and shared with the Community.
!!! Existing terminology sources

A CoP is integrating information from many disciplines and along many facets (places, times, living beings, chemical substances, diseases, etc.).

''The first service from ASKOSI is to gather the different existing vocabularies, where they are, and to make them all accessible in one place.''
!!! Existing documents and information catalogs

Those vocabularies are used to index different catalogs of documents or relevant information. They are often used to filter those sources to keep only specific topics which interest the CoP.

''For every concepts of every gathered vocabularies, ASKOSI provides complete tables of how much they are used in different applications (and roles in those applications).''
!!! Building a common classification inline with the CoP missions

A thesaurus is a vocabulary and a classification hierarchy. To classify, to organize accesses to documents and information, is an activity done within the context of a mission. An ontology tries to be "true" in a very large context, a thesaurus is often much more dependent on the foreseen needs of the users.

''ASKOSI proposes to build small thesauri tailored for a CoP. They can be linked by equivalences relations with concepts in broader vocabularies (e.g. MeSH, CatalogOfLife, DBpedia, etc.): %%( background-color: rgb(175, 238, 238); )a search can be built navigating in the CoP specific vocabulary and be expanded using the broader vocabularies%%.''

Aligning classifications do ease searches and filtering across multiple documents and information catalogs.
!!! Continuous collaboration to keep the common classification up to date

Indexing documents, organizing information, retrieving interesting resources are demanding tasks for which a documentation and an efficient feedback collection mechanism must be available.

''ASKOSI links each concept to a Wiki page where the scope of the concept can be explained and any usage problem can be reported and discussed.''

''Graphical view of the concepts~' relations is also supporting discussions about thesaurus organisation.''
!!! Centralised tracking and tagging

<<A given data / documents set is mainly accessed in three ways (often combined): >>
<<# by indexes (word, concepts) (what is pertinent to my needs?)>>
<<# by peers recommendation (what is hot?) >>
<<# by recent availabilty (what is new?)>>
<< >>
<<''ASKOSI aims to integrate independant applications from the user point of view. It brings the user from one topic to all its references. %%( background-color: rgb(175, 238, 238); )It will also record and share "tags" to let users recommend documents / information to their peers. It will also record modifications and usage to show what is new or popular.%%''
<<

tobedeletedwhenpossible

Christophe Dupriez — 2012-01-27T09:59:58Z

Christophe Dupriez changed this page on Fri Jan 27 10:59:58 CET 2012:

News_blogentry_180112_1

Christophe Dupriez — 2012-01-27T09:23:40Z

Christophe Dupriez changed this page on Fri Jan 27 10:23:40 CET 2012:

!!! Step by step explanation...

To explain the context of the needs for ASKOSI, [a little schema build itself step by step|http://askosi.org/context]. Just the spacebar or click the schema to advance from one step to another. The whole text is displayed at the end. An [ASKOSI story] is also in preparation.

JITA Maintenance

Christophe Dupriez — 2012-01-13T13:23:45Z

Christophe Dupriez changed this page on Fri Jan 13 14:23:45 CET 2012:

!!! Welcome to the initiative of the E~-LIS community to improve JITA ~!

JITA is the vocabulary to index and search in the [E~-LIS|http://eprints.rclis.org/handle/10760/3619] Open Repository.

[A manual for indexers could be useful.|Indexing E-LIS contributions using JITA]

>>Part of ASKOSI Wiki is dedicated to the JITA <<classification~~classification.~~>> <<itself:~~Those~~ <<those Wiki pages are interlinked with the JITA classification as it is stored in the [ASKOSI software|http://www.destin.be/scheme/view.jsp?scheme=jita]. The community of JITA users and maintainers are invited to register to this Wiki and to contribute their observation, examples, suggestions in the pages dedicated each individual JITA concepts.

For instance the JITA entry "Relationship of library and information science with other fields such as computing and communication science and cognitive science" as the permanent code THCO.

It can be examined in ASKOSI software, looking at [http://www.destin.be/askosi/concept.jsp?concept=jita(underline)THCO|http://www.destin.be/askosi/concept.jsp?concept=jita_THCO]

It can be commented and discussed by pressing there the button "Concept Discussion" or by going at the [jita(underline)THCO|jita_THCO] page in this Wiki.
!! Languages (tr, el, nl, cs, fr, it, ro, ca, pt, pl, es, en, ar):
* The language of ASKOSI software interface is english only for now.
* The language of ASKOSI Wiki User interface is the one you select in "My Preferences" (link at the upper right corner).
* The language of vocabulary terms displayed in both programs, is the one you select has your prefered language in your browser configuration. JITA is in so many languages: enjoy ~!
!! JITA Initiatives:
* JITA on FAO AIMS:
*# [Theoretical and General|http://aims.fao.org/aos/jita/T]
*# [User oriented, directional, and management functionalities|http://aims.fao.org/aos/jita/P]
*# [Objects, Pragmatics and Technicalities|http://aims.fao.org/aos/jita/O]
* Current JITA for inspection by the community: [http://www.askosi.org/jita.xml]
* E~-LIS Access using Graphs from JITA: [http://www.askosi.org/jita]
* __JITA in ASKOSI experiment: [Jita in Askosi]__
* Recommended Reading for potential contributors: [JITA Bibliography]
* [Improving JITA]
* Mapping to LinkedData (LOD):
** JITA is used to organize [E~-LIS|http://eprints.rclis.org/handle/10760/3619] collections
** Nearly two third of JITA has been mapped to DDC by Mathias Loesch at University of Bielefeld: [Project presentation|http://wiki.ub.unibi.de/wikifarm/fields/ub_edvmain/field.php/Oeffentlich/AlexEnglishSum], [Article|http://journals.tdl.org/jodi/article/view/1765]
** Manual mapping of suitable JITA concepts to [DBpedia|http://dbpedia.org/] and [Docupedia|http://docupedia.es/] are being done manually by the community: this Wiki could be used
** Those mappings will be included as LinkedData in JITA SKOS/RDF and will be improved as a part of JITA Maintenance project.
* Tooling:
** Integration of JITA Maintenance Wiki with JITA (one page per JITA concept or proposed concept)
**# [Theoretical and General|jita_T]
**# [User oriented, directional, and management functionalities|jita_P]
**# [Objects, Pragmatics and Technicalities|jita_O]
** We now have the same tools than Belgium Poison Centre. Example: [http://www.askosi.org/example/SAQ.pdf]
*** SAQ is for "Sometime Asked Questions", the name of Belgium Poison Centre Wiki.
*** There can be one page (and only one) for each concept in the thesauri (plants, animals, substances,...).
*** Each page begins with a table situating the concept in its thesaurus. Here we learn that "Vipera Berus":
**** is a kind of "Vipera SP",
**** has to related concepts (the antibodies and the extracts)
**** has four narrower concepts
**** is discussed in 24 scientific articles (clicking on terms brings to the whole thesaurus entry where one can ask for a schema).

Indexing E-LIS contributions using JITA

Christophe Dupriez — 2012-01-13T13:19:30Z

Christophe Dupriez changed this page on Fri Jan 13 14:19:30 CET 2012:

!!! Indexing E~-LIS contributions using JITA

Indexing your contributions to E~-LIS means, for each article contributed, to list the subjects it covers.

The subjects comes from a pre~-defined and controlled list: the JITA vocabulary.

[{Image src='JITA Maintenance/JITA-VUE.png' style='width: 1200px; height: 740px;'}]~~Maintenance/JITA-VUE.png'}]~~

This vocabulary is organized in 10 facets: for each, you will have to assess if your article is investigating LIS in that dimension and choose if one (and sometimes more than one) entry is well related to your article.

The current facets are:
# ~[Theoretical and General~]: general level
#* A. Theoretical and general aspects of libraries and information
#* B. Information use and sociology of information
# ~[User oriented, directional, and management functionalities~]: intermediate level (socio~-economical and legal issues are included here)
#* C. Users, literacy and reading
#* D. Libraries as physical collections
#* E. Publishing and legal issues
#* F. Management
#* G. Industry, profession and education
# ~[Objects, Pragmatics and Technicalities~]: specific level
#* H. Information sources, supports, channels
#* I. Information treatment for information services, Information functions and techniques
#* J. Technical services in libraries, archives and museums

JITA Maintenance/JITA-VUE.png

Christophe Dupriez — 2012-01-13T13:17:03Z

Christophe Dupriez created this attachment on Fri Jan 13 14:17:03 CET 2012

Parent page: JITA Maintenance
Info page: JITA Maintenance/JITA-VUE.png

Improving JITA

Christophe Dupriez — 2012-01-13T13:11:45Z

Christophe Dupriez changed this page on Fri Jan 13 14:11:45 CET 2012:

JITA was created 10 years ago. A community reviewing effort based on JITA real usage has started.

A first discussion happened in [Valencia, November 3rd|news_blogentry_251211_1/valendia.pdf]

JITA usage in E~-LIS can be seen in the two attached files:
* [Co~-occurrences of JITA entries in E~-LIS|JITAMAT.xls](how many E~-LIS records are indexed by each possible keywords combinations?)
* [Cleaned up list of frequent keywords for each JITA entry|jitakeyfreqsel.xls]

[{Image src='valence.gif'}]