Content management with repository open service interface definition

Ace p.

Order the writing of a tailor-made Computer science Term papers

Free quote online

Thesis Format .pdf

Content management with repository open service interface definition

Download

Read an extract

Reader
Abstract
Contents
Extract

Abstract

Now days the term content management is the key issue with website's design, what to include what not
to include is very crucial problem. Here, in this paper we have shown the way of managing content called assets, which may contain metadata, course materials, assessment items, images, videos etc. The repository open service definition is an oki specification which defines the storing and retrieving of digital content referred to as assets. Here we have shown architecture of repository open service interface definition as well as its usefulness in managing contents. The Repository Open Service Interface Definition (OSID) is an O.K.I. specification which defines the storing and retrieving of digital content, referred to as Assets. OSIDs are programmatic interfaces which comprise a Service Oriented Architecture for designing and building reusable and interoperable
software.

Key-words: Open Service Interface Definition(OSID), Open Knowledge Initiative(OKI), Service
Oriented Architecture(SOA).

Introduction
OSID's - Open service interface definitions
Usage and functions of OSID's
Package org - OSD repository description class summary
Conclusion
References

Get this table of contents for free after login.

Extract

[...] Some useful methods of this interface are copyAssets(), getAssets() etc.[4] 7.2 org.osid.repository.Asset An Asset's definition includes several methods for managing Records in addition to the common ones for display name, description, and id. The management methods are a little more complex than the ones found in the Repository. To start, we have the getDisplayName(), updateDisplayName(), getDescription(), updateDescription(), and getId(). These methods are similar to those found in many OSIDs . A PartStructure has the common methods, getDisplayName(), getDescription(), and getId(). [...]

[...] The Authentication OSID permits an application to abstract the authentication process without having to manage the details of the underlying authentication service AUTHORIZATION The Authorization OSID allows an application to establish and query a user's privileges to view, create, or modify application data, or use application functionality COURSE MANAGEMENT The CourseManagement Open Service Interface Definition (OSID) primarily supports creating and managing a CourseCatalog. The catalog is organized into: CanonicalCourses, which are general and exist across terms; CourseOfferings for CanonicalCourses, which occur in a specific term, have a CourseGradeType1, a Status, etc; and CourseSections for CourseOfferings, which have a meeting location, schedule, student roster, etc. [...]

[...] This is similar to what is done with the Asset, Search, and Status Types. RecordStructures contain PartStructures, which in turn can contain PartStructures. The getPartStructures() method returns the PartStructures in the RecordStructure. The method getFormat() returns a string that describes the format for this RecordStructure. An example of a format is XML. The OSID does not specify any format strings in particular. Which formats to use and how to interpret them is a convention established between the implementation and any applications. [...]

[...] The Repository Open Service Interface Definition abstracts the assembly of assets into a repository as well as a variety of asset description information management.[3] 7. HOW THIS TOGETHER?? INTERFACES WORK A Part contains the data whose structure is defined by a RecordStructure's PartStructure. The getPartStructure() method returns that information. The methods, createPart(), deletePart(), and getParts() provide for managing any Parts in the Part. Parts have an identifier and the getId() method returns it. The getValue() method returns the value of a Part. [...]

[...] Repositories have a set of Types associated with them. The set of unique Asset Types supported by the Repository are returned with the method getAssetTypes(). There are also Search Types, returned by the getSearchTypes() method, that make clear what kinds of searches are support. The RepositoryManager contains a getAssets() method that performs any search. Assets can have a status and the getStatusTypes() method returns the set of supported kinds of status. The getStatus() method returns the status for a particular Asset. [...]

pdf