[crm-sig] CIDOC CRM wiki

Tony Gill tg at artstor.org
Mon May 17 20:32:24 EEST 2004

Hi Efthimios,

Wow, there are lots of cool features! However, since we are taking our first tentative steps into WikiWorld (and will be relying heavily on your time and generosity for setup and maintenance!), I think that a very basic installation would be best all around.

The main CIDOC CRM SIG website will continue to be the primary place for publishing public information; the wiki tool will serve as an online collaborative workspace to prepare content for the main website.

Therefore, I think the only essential component is the Wiki. Some of the other components, such as comments, polls, image galleries, search and notes might be nice, but are not essential. And I can't imagine ever wanting to receive the CIDOC CRM on my mobile 'phone! :-)

Would you be able to host a very basic Tiki server and database for us at your institution?


Tony Gill
Director of Metadata & Cataloguing, ARTstor Inc.
140 East 62nd Street, New York, NY, 10021, USA
t1 (direct): +1 (646) 274-2265,  t2: +1 (212) 838-8400
w: http://www.artstor.org,  f: +1 (212) 223-2778 

> -----Original Message-----
> From: owner-crm-sig at ics.forth.gr [mailto:owner-crm-sig at ics.forth.gr]On
> Behalf Of Mavrikas Efthimios
> Sent: Monday 17 May 2004 10:07 AM
> To: 'crm-sig '
> Cc: 'martin '
> Subject: [crm-sig] CIDOC CRM wiki
> Hello to all,
> I would be glad to set up and maintain the CIDOC CRM wiki for the SIG.
> However, a couple of decisions need to be made by the SIG 
> members before
> setup work can begin:
> a. Location of wiki host server & database.
> b. Choice of wiki software & components.
> In principle, installation and testing of the basic 
> components offered by
> TikiWiki does not take more than a few hours, depending on 
> the server OS
> (making things work properly under Windows-family operating 
> systems can take
> days; most wiki software offerings have been designed for the 
> LAMP framework
> -> Linux, Apache HTTP server, MySQL database, php language). 
> However, the
> integration of advanced components - such as an 
> ontology-driven annotation
> tool, an SVG viewer, hypermedia browsers of different 
> "flavours", etc. -
> with TikiWiki can take much longer.
> In order to help the SIG members formulate their opinion on a 
> & b, I copied
> some basic information on TikiWiki (overview, components/features and
> installation requirements) from the CMS website and manual:
> ---
> Tiki CMS/Groupware (aka TikiWiki) is a powerful open-source Content
> Management System (CMS) and Groupware that can be used to 
> create all sorts
> of Web Applications, Sites, Portals, Intranets and Extranets. 
> TikiWiki also
> works great as a web-based collaboration tool. TikiWiki is a 
> multi-purpose
> package with a lot of native options and sections that you can
> enable/disable as needed. It is designed to be international, 
> clean and
> extensible.
> Major features include articles, forums, newsletters, blogs, 
> a file/image
> gallery, a Wiki, drawing applet, trackers, a directory, 
> polls/surveys and
> quizzes, a FAQ, chat, a banner management system, Webmail, a calendar,
> Ephemerides, maps, charts, Mobile Tiki (PDA and WAP access), 
> RSS feeds, a
> category system, a theme control center, workflow, live 
> support, Shoutbox,
> ACLs, and more.
> The Wiki
> The Wiki is a collaboration environment where the users can 
> edit the pages
> they read. Links to wikipages are created automatically using 
> capitalized
> words smashed together (e.g., WikiPage). A special editing 
> syntax is used to
> provide features such as bold text, images, external links, 
> etc. A history
> is kept for each page so admins can view diffs and rollback a 
> page to a
> previous version if a user breaks a page. Wikis can be used for
> documentation, support, intranets, and many other uses. The 
> Tiki Wiki system
> has all the normal features Wikis have plus a lot more.
> Image Galleries
> Image galleries are collections of images. Users can create 
> galleries and
> upload images to private or public galleries. You can select 
> the number of
> thumbnails to appear in gallery rows/files as well as the 
> thumbnail's size.
> Thumbnails are automatically created by Tiki; you don t have 
> to upload them.
> Galleries can be used for albums, stories, showrooms, and many other
> applications.
> Articles and submissions
> The articles & submissions system allows editors to publish 
> articles in a
> Content Management System (CMS). Articles can belong to a 
> topic and topics
> can be administered. The articles can use an image or the 
> topic image. You
> can set the publishing date of any article--allowing you to 
> program articles
> for the future. The article content can use the Wiki syntax 
> or regular HTML.
> Links and images in articles are automatically cached to 
> prevent content
> that resides in other pages from disappearing. The CMS system 
> also accepts
> submissions. Users can send proposed articles and the editors 
> can edit,
> remove, or approve submissions as articles. 
> There is an articles home page where the last n articles are 
> shown. You can
> configure how many articles are shown.
> Blogs
> Blogs are great and they are very popular today. A weblog is 
> a collection of
> posts ordered by date. It's like a journal on the web. A post can be a
> comment about something the user did, a review, a thought, 
> anything. The
> Tiki Blogs system is quite powerful. Users can create blogs 
> and, of course,
> post entries into private or public blogs. If you want, you 
> can choose a
> Blog and make it appear as the home page of the site. Tiki 
> also implements
> the Blogger XMLRPC interface, allowing you to use applications such as
> wBloggar or Blogbuddy to manage and edit weblogs.
> JgraphPad drawings
> JGraphPad is a powerful java drawing applet.
> Mobile Tiki
> Mobile Tiki permits web developpers to offer a WAP / PDA / 
> i-mode version of
> their site with the same content and without any extra work! Tiki has
> partnered with the innovative HAWHAW toolkit. Currently, wiki 
> pages and
> blogs are available. More features (forums, directory, etc) 
> to be added in
> the near future.
> Voice Tiki
> TikiWiki is voice-enabled by HAWHAW. This feature makes 
> TikiWiki a perfect
> tool to create voice services fast and easy. Voice browsers 
> are provided by
> VoiceXML providers and are typically connected to both the 
> public telephone
> network and the internet. HAWHAW and TikiWiki are optimized 
> for the Voxeo
> voice browser.
> Banner ads
> Banners are a common way for advertisements and notices to be 
> displayed on a
> Web page. The Tiki banners system supports image and HTML 
> banners (used in
> banner exchange sites) and Text Ads. Banners are assigned to 
> "zones" in your
> application. There're a lot of configurable options for 
> banners--such as
> maximum number of impressions, weekdays when the banner can 
> be displayed,
> hours, etc. Banner clients are normal Tiki users and they can 
> view banners
> assigned to them accessing a page where banner stats are displayed.
> Including banners in Tiki is easy--using a very simple syntax in any
> template or user module.
> Dynamic Content System
> The Dynamic Content System (DCS) is a very simple concept. 
> You can edit
> blocks of HTML code or text from a admin screen and you can 
> display a block
> in any Tiki template or user module. Updating the block 
> content will update
> the template. You can also program block content by 
> date--storing several
> blocks to be displayed in future dates. This simple system 
> adds a lot of
> flexibility to Tiki. You can display anything you like anywhere in the
> screen and you can set up portions that can be changed or that change
> automatically along time.
> File Galleries
> The file galleries section of Tiki is a very flexible 
> download manager. You
> can create/edit file galleries, which are collections of 
> files. Using the
> permission system, you can control who can create file 
> galleries, upload
> files and download files. Statistics are recorded for each download.
> Rankings are defined for the top-downloaded files, most-visited file
> galleries, and last-uploaded files. Modules are also 
> available to display
> last-changed file galleries, last-uploaded files, 
> top-downloaded files and
> top-visited file galleries. You can use file galleries to 
> distribute free
> multimedia files (mp3's, avi's, etc) and software (versions, patches,
> releases) and to add files that users can download from Wiki pages,
> articles, weblog posts, etc.
> Featured Links
> The featured links section manages links. You can enter as 
> many links as you
> want and a user module displays the links in the order that you want.
> Clicking the links will open the site in a frame inside the 
> central section
> of Tiki. Statistics are kept about the number of times that 
> featured links
> are visited and you can automatically order featured links by 
> the number of
> hits they have.
> Comments
> Comments are used to provide user-feedback to many Tiki 
> features. Users can
> comment on Wiki pages, image galleries, file galleries, 
> articles and polls.
> The comment system can be configured to allow users to vote 
> on comments. A
> karma system mantains a level for each user. The level 
> improves when a user
> comment is voted on by another user. Good qualified users 
> votes add more
> points to a comment than users who didn't get good 
> qualifications. Comments
> can be displayed/hidden using simple controls and the user 
> can control how
> to sort votes, the number of votes to see by page and the 
> minimum threshold
> (score) for a vote to be displayed.
> Forums
> Forums are a must-have feature for a community site. A forum 
> is a collection
> of topics containing user messages. Using Tiki you can 
> configure as many
> forums as you want and establish permissions to determine who 
> can create
> forums, admin forums, create topics, post messages, vote on 
> messages, etc.
> Individual permissions can be set for forums so you can have 
> private forums
> only visible to some user groups. The forums section in Tiki has many
> advanced features such as auto-prunning to prevent the base 
> of messages
> growing too big, flood-preventing, sticky topics, locked topics, etc.
> ChatRooms
> Admins can create chat channels that users can join. Once in 
> a channel,
> users post messages that are broadcast to all the users in the same
> chatroom. Chatroom messages are updated at a given interval 
> that can be
> configured for each chat channel (you may want one channel to 
> refresh faster
> than others).
> Communications center
> The communications center is a feature not found in many CMS systems.
> Basically, it lets you send/receive objects to and from other 
> Tiki-powered
> sites. You can control who can send you objects and who can admin the
> received objects. A special inbox is used to examine received 
> objects and
> you can edit the objects, remove them or accept them from this inbox.
> Accepted objects will appear as normal Tiki objects. For 
> example, if you see
> a nice Wiki page about a specific topic or a set of pages 
> useful to your
> site you can ask for them and use this feature to receive the 
> pages from
> another site. The communications center is based on an XMLRPC api to
> send/receive objects so you can build desktop applications or 
> adapt existing
> systems to interact with your Tiki site.
> Polls
> Polls are a common feature in user-community sites. Using Tiki you can
> create as many polls as you want and display from zero to n 
> polls in the
> Tiki pages. You can also have a set of several active polls 
> and display only
> one poll in a page. In that case, Tiki will rotate through 
> the set of polls.
> Users with the right permission can see poll results, examine 
> old polls and
> vote in any poll that is not closed.
> Category system
> Categories are a way to classify Tiki objects (Blogs, Image galleries,
> Articles, Polls, Forums, Wiki Pages, File Galleries). You can create a
> category tree with as many sub-categories as you want. Any 
> Tiki object can
> then be added to one or many categories. The user will be 
> able to use a
> category browser--navigating the category tree with links to 
> the objects in
> the category. This can be used to let the users find all the 
> information
> your Tiki site has about a specific topic/subject regardless if the
> information is in an article, a weblog or a file gallery.
> FAQs
> FAQs (Frequently Asked Questions) are lists of common 
> questions and answers
> about a specific topic. FAQs are widely used in online 
> communities to group
> popular questions and have them solved without the need to 
> repeat the same
> answer multiple times. Tiki allows you to create as many FAQs 
> as you want
> with any number of questions in each FAQ. Optionally, users 
> may be allowed
> to suggest questions to be answered, which admins/editors can 
> reply to or
> delete.
> Quizzes
> Quizzes can be used for fun, for trivia, for contests or for creating
> courses and e-learning sites. A quiz is made of a number of 
> multiple-choice
> questions, each option in a question can be assigned positive 
> or negative
> points. After the user takes a quiz Tiki computes the score 
> and an answer
> can be displayed to the user depending on his or her score. 
> You can control
> if quizzes can be repeated and you can indicate a time limit 
> for quizzes. If
> you want, quiz results can be stored and you can review the results.
> Statistics are always stored for quizzes--keeping track of 
> the results of
> each quiz.
> RSS feeds
> Tiki is remarkably flexible when it comes to RSS. It can both display
> external RSS feeds from other sites in user modules and elsewhere and
> syndicate its activities (blogs, articles, forums, Wiki and 
> galleries) via
> RSS.
> HTML pages
> Tiki offers a simple way for creating pages that will be 
> displayed to the
> users and that can be linked from/to any place in your site. 
> Just create an
> HTML page using the editor and then you can access it using tikipage.
> php?pageName=some. The simple html pages system can be 
> extended with the
> addition of dynamic pages.
> HTML pages dynamic
> A dynamic page is an HTML page where you can use the syntax 
> {ed id=foo} to
> create dynamic sections inside the page. An editor will be 
> automatically
> available to edit each dynamic zone of a dynamic page. 
> Dynamic pages will be
> automatically updated without a browser refresh and without 
> making the user
> refresh the page. So dynamic pages are great for sport scores, stock
> information, real time coverage of events or other uses that you may
> imagine.
> Surveys
> Surveys can be used to gather the opinion of users in your 
> site. You can
> create surveys using different question formats: short-text questions,
> multiple-choice questions, single-choice questions and two 
> different rate
> questions. Users can fill in the surveys and then you and 
> they can check the
> survey's statistical results.
> Trackers
> Trackers are a powerful and flexible tool. Trackers are used to keep a
> record of a collection of items. You can set up what fields 
> items will have
> per tracker. Then you can add/remove items, list items, comment items,
> attach files to items etc. Items can be assigned to 
> user/groups and if the
> item is open it will appear in the user-preferences screen. 
> Trackers/items
> can be monitored by email. You can use trackers for support 
> tickets, feature
> requests, buying orders, bug reporting, feedback reporting, 
> submission of
> news, etc. Many workflows can be modeled using one or more trackers.
> Newsletters
> The newsletters feature allows admin to define as many 
> newsletters as he or
> she wants. Users can subscribe to newsletters and a email 
> confirmation is
> required to prevent spamming. Then admin can send HTML-based 
> newsletters to
> the (confirmed) subscribers. This can be used to communicate 
> site news,
> broadcast site events, etc.
> Directory
> The directory organizes Web links into convenient 
> categories--similar to the
> dmoz open directory project or Yahoo! Users can browse link
> descriptions--navigating the categories by drilling down to 
> increasingly
> specific sub-categories. Or they may search for specific 
> text. Users can
> also suggest links they would like to see added to a 
> directory. Thus, a
> successful directory is built by its Tiki community. Admins, 
> or editors they
> designate, can validate user suggestions before they are posted. An
> unlimited number of categories can be created and they can be 
> related to one
> another--encouraging users to move from one to another. Tiki 
> tracks the
> addition of new links and the amount of traffic they attract. 
> Users can view
> the top-ranked new sites and cool sites (heavy traffic sites) 
> by clicking a
> button. Optionally, directory rankings/stats modules can be 
> displayed in
> Tiki columns.
> Ephemerides
> The ephemerides section can be used to associate one or many 
> images and/or
> texts for each day of the year. Users can then browse the associated
> information for a particular day and a module can be used to 
> display the
> information for the current day. This can be used to display 
> comic strips,
> quotes, national holidays, and many other ideas.
> Shoutbox
> A module for users to put instant comments on your Tiki--much like a
> graffiti feature.
> Search
> Comb through a Tiki site to find just the information you 
> want. Search picks
> through forums, image/file galleries, link directories, CMS 
> articles, blogs
> and Wiki pages to find the terms you specify. And Tiki compiles search
> statistics for admins so that they may keep an eye on what 
> users want from
> their sites. There are two forms of searching: regular and full text.
> Full-text searching sorts results by the relevance of the match to the
> search query. Also, search results will be ordered first by 
> relevance, and
> then by section (Wiki, blog, etc.). Regular, non-full-text searching
> continues to sort first by section, and then by hits.
> Games
> Games may be incorporated into Tiki to add a bit of fun to 
> the site. The
> games are graphically based and created with Macromedia Flash 
> or Director.
> Live Support System
> Live support puts you on-call when your users need you. With 
> the click of a
> button, a user may request help from a tech support operator. The live
> support module automatically opens a chat window between user 
> and operator.
> Galaxia Workflow Engine
> The Workflow Management Coalition defines workflow, in 
> general, as "The
> automation of a business process, in whole or parts, where documents,
> information or tasks are passed from one participant to another to be
> processed, according to a set of procedural rules." Galaxia 
> is an "activity
> based" workflow. Workflow processes are implemented as a set 
> of activities
> that must be completed to achieve some result.
> Charts
> Charts are sort of like surveys.
> My Tiki section
> Logged-in users can enjoy many convenient features in the 
> MyTiki section.
> All of these features can be enabled/disabled by admin. Some 
> features can't
> be offered to users without a valid login name and password, 
> so they are
> only present when a user has logged in to Tiki using a valid 
> username and
> password, the features that are available to registered users 
> are grouped in
> the MyTiki section.
> Webmail
> The Webmail feature provides a Web interface for users' email 
> accounts.
> Users can set an account by indicating the POP3 and SMTP 
> servers to use.
> Then they will be able to read mails, send mails, manage 
> attachments, manage
> contacts and other regular Webmail features. Tiki can read 
> and write HTML
> based emails as normal Webmail programs do.
> Inter-User Messages
> Users can send messages to other Tiki users and 
> read/reply/remove messages
> in their mailboxes. Messages can have a priority setting and 
> the user may
> choose to be notified by email when important messages are 
> received by Tiki.
> The user can close his or her mailbox from this user 
> preferences screen and
> he or she will not receive messages. Messages can be flagged 
> for follow up.
> Admins can send broadcast messages to all the users in a Tiki 
> site. A module
> to display the number of unread messages is also included. User with
> permission can send messages to all the members of a group.
> User notepad
> Using the notepad users can write, upload, download and read 
> notes. Notes
> can be read as raw text files or as Wiki pages interpreting 
> the Wiki markup
> syntax. The user-quota that admin can control is used to set 
> the maximum
> size that user notes can take.
> User tasks
> User tasks let the user set-up to-do tasks and then view the 
> current tasks,
> mark them as done or delete them. A task can be programmed to 
> be activated
> in future date. A module that lets the user manipulate tasks 
> is provided.
> User files
> Users can store personal files on a Tiki site. They can 
> upload files and
> then download them when they want. A quota can be setup to control the
> maximum size of personal files per user.
> User calendar
> The calendar can be used at user level to enter events for 
> any date. Events
> can be viewed in daily or weekly views or as a list. 
> Reminders can be used
> to notify the user about an event some time before it starts. The Tiki
> calendar can be imported and exported from Outlook.
> User menus
> Using user menus the user can add personal items to the User 
> Menu section in
> the application menu. An option is provided to let the user 
> automatically
> add all the top-level bookmarks to his or her personal menu.
> User preferences
> User preferences let the user select all the user-level 
> preferences for the
> site: personal avatar, time zone, theme, language, etc.
> User bookmarks
> User bookmarks let users bookmark internal or external pages, 
> create folders
> and organize their personal bookmarks in folders. Bookmarks 
> can be cached if
> that option is enabled. A module is provided to let the users 
> see their
> bookmarks, navigate through them, and add new bookmarks.
> User modules
> Modules are the boxes you see in the left and right side bars of the
> application. The user modules section lets the users hide or 
> show available
> modules of a Tiki site and configure their positions. Modules 
> administrators
> can make many more predefined modules available and create 
> their own using
> HTML. PluginModule is a plugin that allows modules to be 
> included in Wiki
> pages.
> User watches
> User Watches monitor content that users are interested in. There is a
> Watches page in User preferences to organize this monitoring. 
> Currently,
> blogs, Wiki pages and forums can be monitored.
> Newsreader
> The newsreader can be used to let the user browse news from any NNTP
> (usenet) site. They can read news and mark articles as read 
> to know when new
> posts appear.
> TikiWiki is fairly easy to install thanks to an install 
> script. However, it
> is not yet a double click experience windows users are used to.
> TikiWiki relies on three major external applications to run:
> -PHP (scripting language)
> -Apache (web server)
> -MySQL (database)
> An application such as phpMyAdmin is also extremely useful in order to
> administer the MySQL database via a web browser.
> Once these external applications are installed, a TikiWiki 
> database must be
> created and a TikiWiki MySQL user must be created with the appropriate
> priviledges.
> After the working environment has been setup, all 
> administration operations
> can be performed online within TikiWiki, either locally or remotely.
> ---
> > Tony Gill wrote:
> > ------
> > Hi Efthimios,
> > 
> > That's great! Yes, please set up a CIDOC CRM wiki for us.
> > Many thanks for this very generous offer!
> > 
> > Cheers,
> > 
> > T.
> > ------
> >
> > 
> > Efthimios Mavrikas wrote:
> > ------
> > Good afternoon,
> > 
> > I would just like to inform the SIG members that CILab is 
> > currently using a wiki collaborative environment for its site
> > and a couple of projects run by the laboratory.
> > 
> > Please let us know if we could be of any help in the setup
> > and maintenance of a CIDOC CRM wiki.
> > 
> > CILab (http://webdance.ath.cx/wiki/)
> > based on the TikiWiki CMS/Groupware (http://tikiwiki.org/)
> > 
> > Regards,
> > Efthimios Mavrikas
> > ------
> > 
> > 
> > Tony Gill wrote:
> > ------
> > (...)
> > I suggested setting up a CIDOC CRM Wiki so we could 
> > collaborate on producing documentation such as mappings.
> > (...)
> > ------
> > (...)
> > I *might* have promised to research potential software tools
> > -- a goodstarting point is available here:
> > http://en.wikipedia.org/wiki/Wiki_software
> > (...)
> > ------
> > 

More information about the Crm-sig mailing list