Loading...
 
(Cached)

Object ownership and freshness

The idea


The idea is that Tiki objects (wiki pages, blogs, etc.) will optionally have owners, an update frequency and a freshness, i.e., how long ago it has been updated. Then, when an object becomes too old relative to its update frequency, Tiki will send emails to the owner reminding about the need to update it.

It'll be an extension to the Monitoring lib (lib/user/monitorlib.php), that notifies users upon certain changes in objects.

How it will work


Let's take the example of a wiki page. When creating or editing a wiki page, on the Properties tab the user will be able to indicate an owner (user selector) and the update frequency in days. The operating user will be the default owner.

A new console command, e.g. user:sweep-object-freshness, will sweep the objects and send emails to the owners telling them about the need to update.

A new Relation, e.g. tiki.user.object_owner will be used to link users to objects. A new Attribute, e.g. tiki.user.update_frequency, will store the object's update frequency in days. See: Object Attributes and Relations.

New Preferences, e.g. user_ownership_enable and user_ownership_default_frequency etc, will be created for this feature (seems to make sense to keep them all in lib/prefs/user.php to me ).

Questions and Plans

  • Should we have multiple owners and multiple update frequencies? (each owner with an update frequency, if so, how?)
  • Let's start with Wiki Pages in trunk for Tiki 21.x but to backport to 20.x when stable
  • I think there needs to be a global setting for update frequency and then the attribute can override this global setting
  • I think there needs to be an option to send an email to a group of admins (a default to be specified globally and as another attribute (tiki.user.object_ownergroup) i.e. a group responsible) - maybe need to support multiple groups - by creating multiple relations? Should the pref for the default be added to the setting in the relations, or added to it? I can see both use cases
  • Would it support multiple owners users (by creating multiple relations)? Or must we create a group and use tiki.user.object_ownergroup?
  • I think it's related but a separate feature from Goals and Recognition but perhaps the Goals and Recognition could be enhanced to use the owner/ownergroup relation or "keeping your object updated" could be setup as a goal in the future.
  • I like that it can specify specific owners as this is often different from the people actually last_modified the item.
  • I like that it ties into monitorlib so goes through Notifications
  • How would the owner (or one of the owners) mark it as "updated" and how would we record who marked it as such? Note that merely editing it may not mean it's in an "updated/fresh" state. Besides other people (depending on perms) may be able to edit it too...
  • Maybe "owner" could be too strong a title sometimes? Curator, Manger, Keeper? In some situations, it could be better to encourage participation on wiki pages. If there was an "owner" it might intimidate?
  • Would be great to see what pages lacked an owner, perhaps with a little "adapt me" button or something like that
  • What pages someone "owned" could be good information to show on the profile tab.
  • Perhaps if a page is not marked as updated after a certain point, ownership could be receded


I'll detail it further soon, have to leave now :-)


Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting
Administration
Ajax
Articles & Submissions
Backlinks
Banner
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution
Cookie
Copyright
Credits
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
DogFood
Draw
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Group
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping
Mobile
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Packages
Payment
PDF
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Scheduler
Score
Search engine optimization (SEO)
Search
Security
Semantic links
Share
Shopping Cart
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags
Task
Tell a Friend, alert + Social Bookmarking
Terms and Conditions
Theme
TikiTests
Timesheet
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
Webmail and Groupmail
WebServices
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives
WYSIWTSN
WYSIWYCA
WYSIWYG
XMLRPC
XMPP




Useful Tools