Content for one: developing a personal content management system Export

@inproceedings{5461, abstract = {You may have browsed or searched one of the large Content Management Systems that store and display useful information; many universities, departments, and library research desks have turned to these to manage both their long-term reference materials and daily-changing data. What if we'd like to manage our own content, but our staff consists of one overworked, time-challenged, long-term-memory-impaired worker: ourself?My own information storage system was "heap-based:" several overflowing desktops of stacks of papers, journals, post-its, and scribbled memos. I needed something better, but didn't have anyone to give this project to and only a modest amount of time to devote to a new project myself.I decided to look at a range of open-source Content Management Systems (CMS) and compare freely-available packaged systems with a completely handmade system based on PHP and MySQL -- all topics with which I had little or no experience.Advantages to setting up a CMS like this (beyond organizing your own data) include gaining familiarity with concepts and systems that are likely to be increasingly important in the future. You may, if you wish, become a mentor to others with the same needs. The goal is to allow the wide-spread sharing of ideas and content without having to spend a lot of time fooling around with the technical details of presentation - a useful tool many people might be interested in.I hope my experience and conclusions will help you decide if a CMS is the answer to your data problems, and which path might be the best route for you to take.}, author = {Simpson, Doug L.}, citeulike-article-id = {3300426}, citeulike-linkout-0 = {http://dx.doi.org/10.1145/1099435.1099512}, citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1099435.1099512&coll=Portal&dl=ACM&CFID=1316299&CFTOKEN=76689082&backfrombind=1}, doi = {10.1145/1099435.1099512}, isbn = {1-59593-200-3}, journal = {Proceedings of the 33rd annual ACM SIGUCCS conference on User services}, keywords = {calendars, cms, content, documentation, prosem}, number = {Monterey, CA, USA}, pages = {338--342}, posted-at = {2008-09-20 21:54:14}, priority = {2}, publisher = {ACM}, title = {Content for one: developing a personal content management system}, url = {http://dx.doi.org/10.1145/1099435.1099512}, year = {2005} }

TY - CONF ID - 5461 L3 - citeulike-article-id:3300426 N2 - You may have browsed or searched one of the large Content Management Systems that store and display useful information; many universities, departments, and library research desks have turned to these to manage both their long-term reference materials and daily-changing data. What if we'd like to manage our own content, but our staff consists of one overworked, time-challenged, long-term-memory-impaired worker: ourself?My own information storage system was "heap-based:" several overflowing desktops of stacks of papers, journals, post-its, and scribbled memos. I needed something better, but didn't have anyone to give this project to and only a modest amount of time to devote to a new project myself.I decided to look at a range of open-source Content Management Systems (CMS) and compare freely-available packaged systems with a completely handmade system based on PHP and MySQL -- all topics with which I had little or no experience.Advantages to setting up a CMS like this (beyond organizing your own data) include gaining familiarity with concepts and systems that are likely to be increasingly important in the future. You may, if you wish, become a mentor to others with the same needs. The goal is to allow the wide-spread sharing of ideas and content without having to spend a lot of time fooling around with the technical details of presentation - a useful tool many people might be interested in.I hope my experience and conclusions will help you decide if a CMS is the answer to your data problems, and which path might be the best route for you to take. IS - Monterey, CA, USA JF - Proceedings of the 33rd annual ACM SIGUCCS conference on User services SN - 1-59593-200-3 EP - 342 TI - Content for one: developing a personal content management system PB - ACM SP - 338 KW - calendars KW - cms KW - content KW - documentation KW - prosem AU - Simpson, Doug PY - 2005/// UR - http://dx.doi.org/10.1145/1099435.1099512 ER -