Skip to main content

Taxonomy Engineering Roadmap

Taxonomy

Taxonomy, is the classification of organisms in an ordered system that indicates natural relationships.

Purpose:

Taxonomies are normally used to facilitate access to information. For the most of tasks and purposes the Taxonomy will be used to connect, relate and classify content. The Taxonomy will enhance content categorization and organization in addition to the ease of access and search.

Planning

The Taxonomy should reflect the objectives of the project. It should be produced by a cross-functional team which includes business, technical, information management, subject matter experts and content creation stakeholders. The Taxonomy implementation and usage in the project will be defined.

Design

The design phase will include the below steps:

Identify, gather and review resources

A set of verbs, nouns, terms and vocabularies will be collected. This list will be reviewed and refined by the ad-hoc team created in the planning phase. A final list should be defined.

Ontology Engineering

The vocabularies will then be ontology engineered by the Information Systems expert with help from the domain subject matter expert. The Ontology will consist of hierarchy of concepts, terms and relations.

Implementation

The domain Ontology will then be used to organize inventory and website content. This will be done by the content publishers. The ontology will be transformed into set of categories, labels and meta-data.

Production

The content publishers will add the set of categories, labels and meta-data to the content management system. This step is done before adding any content.

Training


The content publishers will be trained how to use the Taxonomy when publishing content and will be also trained how to enhance improve or modify the taxonomy based on technology and requirements change and evolvement.

Comments

Popular posts from this blog

Top Google Adsense Alternatives

Google Adsense is a web tool that allows publishers in the Google Network of content sites to automatically serve text, image, video, and rich media adverts that are targeted to site content and audience. These adverts are administered, sorted, and maintained by Google, and they can generate revenue on either a per-click or per-impression basis.  Google servers advertisers using google adwords platform, while adsense is the publishers platform. Google Adsense is the top Ad Publishers platform over the web ranking number one in web advertising industry. Adsense offers contextual advertisements that covers web sites, blogs, games, videos, mobile browsing etc. What made Google Adsense no. 1 is the reliability, stability, variety of services and large number of publishers including google it self. Also google has a fair platform that detects invalid clicks so google successfully protects its advertisers and also offers its best publishers top CPC. Two reasons are behind people think

CFLDAP Add Active Directory User to a Group

I was trying to add a user to a group and had lots of code formatting etc. I was unable to find a straightforward code to help me. I have prepared the below code to help you using CFLDAP and also I will give you an alternative way using the dsmod command line. Lets start first with the CFLDAP: Now lets add an active directory user to a group using command line: When I wrote the above code I added a bulk list of users to a certain Active Directory group. Sometimes the CFLDAP failed so in the cfcatch I called the dsmode using the cfexecute. Why? Some of the user CN names contained special characters like 'bracket (' this caused an error when using the cfldap to add users to the groups so I had to use the cfexcute which succeeded.

ERROR: cross-database references are not implemented

You face this error while trying to query two tables from difference databases in Postgres, as Postgress is unlike SQL Server, you can't join two tables from different databases. Instead you may have One Database with Two different Schemas . Schemas group your data tables separately and give you the flexibility to query and join tables from across schemas in the same Database. So if you have DB1 and DB2, you need to move the tables in DB2 to DB1 but in a new schema. If you are using the public schema in DB2 you need to change the name:   alter schema public rename to new_schema_name ; create schema public ;   Now Backup your Schema: $ pg_dump --format custom --file "my_backup" --schema " new_schema_name " "db2" $ pg_restore --dbname "db1" "my_backup" Your Done. If you have any question please let me know.