Ontology-Supported Web Content Management

2005 ◽  
pp. 203-223
Author(s):  
Geun-Sik Jo ◽  
Jason J. Jung

This chapter introduces the ontology-supported Web content management. Since the Web was regarded as one of the most important tools for searching relevant information, many studies have been attempting to develop efficient and accurate management of Web content and resources. We have been focusing on how to exploit the ontology to support semantic conceptualization of information on the Web. Especially, the emergence of semantic Web emphasizes the importance of the ontological processes. In this chapter, we will mention content management systems on the semantic Web, and then, we will introduce two applications from viewpoints of personalized content and electronic commerce as case studies.

Database ◽  
2019 ◽  
Vol 2019 ◽  
Author(s):  
Lars Vogt ◽  
Roman Baum ◽  
Philipp Bhatty ◽  
Christian Köhler ◽  
Sandra Meid ◽  
...  

Abstract We introduce Semantic Ontology-Controlled application for web Content Management Systems (SOCCOMAS), a development framework for FAIR (‘findable’, ‘accessible’, ‘interoperable’, ‘reusable’) Semantic Web Content Management Systems (S-WCMSs). Each S-WCMS run by SOCCOMAS has its contents managed through a corresponding knowledge base that stores all data and metadata in the form of semantic knowledge graphs in a Jena tuple store. Automated procedures track provenance, user contributions and detailed change history. Each S-WCMS is accessible via both a graphical user interface (GUI), utilizing the JavaScript framework AngularJS, and a SPARQL endpoint. As a consequence, all data and metadata are maximally findable, accessible, interoperable and reusable and comply with the FAIR Guiding Principles. The source code of SOCCOMAS is written using the Semantic Programming Ontology (SPrO). SPrO consists of commands, attributes and variables, with which one can describe an S-WCMS. We used SPrO to describe all the features and workflows typically required by any S-WCMS and documented these descriptions in a SOCCOMAS source code ontology (SC-Basic). SC-Basic specifies a set of default features, such as provenance tracking and publication life cycle with versioning, which will be available in all S-WCMS run by SOCCOMAS. All features and workflows specific to a particular S-WCMS, however, must be described within an instance source code ontology (INST-SCO), defining, e.g. the function and composition of the GUI, with all its user interactions, the underlying data schemes and representations and all its workflow processes. The combination of descriptions in SC-Basic and a given INST-SCO specify the behavior of an S-WCMS. SOCCOMAS controls this S-WCMS through the Java-based middleware that accompanies SPrO, which functions as an interpreter. Because of the ontology-controlled design, SOCCOMAS allows easy customization with a minimum of technical programming background required, thereby seamlessly integrating conventional web page technologies with semantic web technologies. SOCCOMAS and the Java Interpreter are available from (https://github.com/SemanticProgramming).


Information ◽  
2021 ◽  
Vol 12 (7) ◽  
pp. 259
Author(s):  
Ioannis Drivas ◽  
Dimitrios Kouis ◽  
Daphne Kyriaki-Manessi ◽  
Georgios Giannakopoulos

While digitalization of cultural organizations is in full swing and growth, it is common knowledge that websites can be used as a beacon to expand the awareness and consideration of their services on the Web. Nevertheless, recent research results indicate the managerial difficulties in deploying strategies for expanding the discoverability, visibility, and accessibility of these websites. In this paper, a three-stage data-driven Search Engine Optimization schema is proposed to assess the performance of Libraries, Archives, and Museums websites (LAMs), thus helping administrators expand their discoverability, visibility, and accessibility within the Web realm. To do so, the authors examine the performance of 341 related websites from all over the world based on three different factors, Content Curation, Speed, and Security. In the first stage, a statistically reliable and consistent assessment schema for evaluating the SEO performance of LAMs websites through the integration of more than 30 variables is presented. Subsequently, the second stage involves a descriptive data summarization for initial performance estimations of the examined websites in each factor is taking place. In the third stage, predictive regression models are developed to understand and compare the SEO performance of three different Content Management Systems, namely the Drupal, WordPress, and custom approaches, that LAMs websites have adopted. The results of this study constitute a solid stepping-stone both for practitioners and researchers to adopt and improve such methods that focus on end-users and boost organizational structures and culture that relied on data-driven approaches for expanding the visibility of LAMs services.


Information ◽  
2018 ◽  
Vol 9 (2) ◽  
pp. 27 ◽  
Author(s):  
Jose-Manuel Martinez-Caro ◽  
Antonio-Jose Aledo-Hernandez ◽  
Antonio Guillen-Perez ◽  
Ramon Sanchez-Iborra ◽  
Maria-Dolores Cano

Author(s):  
Anne Honkaranta ◽  
Pasi Tyrväinen

Content management is essential for organizational work. It has been defined as “a variety of tools and methods that are used together to collect, process, and deliver content of diverse types” (McIntosh, 2000, p. 1). Content management originates from document management. In fact, a great deal of contemporary content management system functionality has evolved from document management systems. Documents are identifiable units of content, flexibly structured for human comprehension (Murphy, 2001; Salminen, 2003). They have traditionally been considered as containers for organizational content. Document management considers the creation, manipulation, use, publishing, archiving, and disposal of documents as well as the continuous development and design of these activities in organizational domains. In different domains, the requirements for document management differ accordingly. For example, manufacturing companies possess a bulk of technical drawings to be managed, and in e-government organizations, the document content may act as a normative reference that needs to be frozen and archived for long periods of time (Honkaranta, Salminen, & Peltola, 2005). Therefore document management in e-government is commonly split into two types: document management focusing on document production and the records management considering document repository management. Research on document management in organizations has been carried out focusing on a multitude of issues, including document standardization (Salminen, 2003), document metadata (Murphy, 1998), document and information retrieval (Blair, 2002), the social role of documents for organizational groups (Murphy, 2001), as well as document engineering (Glushko & McGrath, 2005). The wide selection of content management systems available has evolved mainly from document management systems (Medina, Meyers, Bragg, & Klima, 2002). They combine into single systems various functionalities developed separately in domains such as library sciences, text databases, information retrieval, and engineering databases. The essential features of document management systems cover: • Library services and version management • Management of user roles and access rights • Text retrieval based on metadata and full-text search • Support for document life-cycle and related work- flows • Management of metadata, as information about documents • Multi-channel publishing for a multitude of devices and print A survey on content management systems revealed that many of the systems still have a monolithic and closed architecture and their ability to adopt proprietary encodings is scarce (Paganelli & Pettenati, 2005). Contemporary content management systems’ support for access management and for customizing workflows for integrating content into organizational processes may be modest. For example, the popular Microsoft SharePoint Server (http://www.microsoft. com/sharepoint/default.mspx) only assigns access rights to folders, not to individual files or units within the files. Content management software may include limited functionality for the design and management of an organization’s Web site. The applicability of the document management approach and the systems for content management have been limited due to an orientation towards using documents as the only unit for managing content. As a consequence of this approach, long documents are difficult to browse through, portions of document content are difficult to reuse in other documents, and long documents are inconvenient for Web delivery (Honkaranta et al., 2005). At least two recent approaches on content management which aim at complementing these weaknesses can be identified. These are Web content management and the use of structured documents in the form of XML.


2009 ◽  
Vol 7 (4) ◽  
pp. 44-51 ◽  
Author(s):  
Michael Meike ◽  
Johannes Sametinger ◽  
Andreas Wiesauer

Author(s):  
Maria-Dolores Cano ◽  
Antonio-José Aledo-Hernández ◽  
Antonio Guillén-Pérez ◽  
Jose-Manuel Martinez-Caro ◽  
Ramon Sanchez-Iborra

Los Sistemas de Gestión de Contenido Web (Web Content Management Systems, WCMS) han ganado mucha popularidad debido a la facilidad que aportan a la hora de crear páginas o portales web, sites de comercio electrónico, etc. En este trabajo se explica de forma resumida cómo es el manejo los WCMS y qué se puede lograr con su uso. Para ello, trabajaremos con tres de los más populares WCMS de tipo open-source empleados hoy en día, Joomla, Wordpress y Drupal, y veremos las ventajas e inconvenientes de trabajar con cada uno de ellos. Con este fin, crearemos tres web iguales en requisitos y funcionalidades, una con cada WCMS, y se analizará cualitativamente la complejidad de cada uno de ellos. Finalmente, realizaremos un análisis básico de seguridad de las webs creadas, informando de sus posibles vulnerabilidades, explicando cómo mejorar su seguridad, qué fallos no debemos cometer y qué WCMS es inicialmente más seguro/vulnerable.


2010 ◽  
Vol 51 ◽  
Author(s):  
Beatričė Andziulienė ◽  
Povilas Narbutas

Give general the most appropriate content management system selection stages of the process, divided into five phases. The last stage of the selection proposed by the Web content management system effectiveness analysis. The analysis of Drupal, Joomla!, Xoops content management systems, efficient use of server resources in three cases: the generation of dynamic pages, cache page and cache page with data compression. Content management systems are compared using the following criteria: the maximum number of queries per second, queries pending, RAM usage, CPU load, database management system load. It was found most effective resources of a server using a Web content management system.


2017 ◽  
Vol 33 (2) ◽  
pp. 63
Author(s):  
Stephen P. Bollinger

Web content management systems (CMSs) are tools to help efficiently manage modern websites. Broadly defined, CMSs are database-driven software packages that allow people who are not HTML experts to create and edit website content, manage revisions and approvals for content, and help reduce the workload of maintaining a website. Within the past five years open source content management systems, created and maintained by a community of software developers and available without charge, have matured to become viable options for libraries that are not information technology juggernauts. Plone1, now in its fourth major release, is one such content management system that is now in wide use by libraries. [...]


Author(s):  
Johan Ragetli

In this chapter key methods and tools available to libraries to manage their Web content are identified. Content in libraries may include subject guides, calendars, hours of operation, and digital collections. Solutions to manage a wide variety of materials and contributors range from enterprise-wide content management systems to homegrown, open source solutions.


Sign in / Sign up

Export Citation Format

Share Document