a Drupal wiki bug solved - flexifilter

Begin

As is known, I began to work on my Always Organizer project located at KickStarter.com.

I began to look into wiki works that have been done for the Drupal platform. Found few good articles that I was not aware of in the past when I was busy working for a not worthing agency - Nebraska Postsecondary.

Anyway. All the thing I learned are going into my wiki - my way of keeping things organized and it is the purpose of my Always Organizer project.

Today, the thing that really made me happy is that I have contributed to the Drupal project - I provided a patch to a Flexifilter issue that have not been resolved for 6 years. See here for detail.

The Flexifilter is one very important component for doing wiki in Drupal. I am glad to contribute and moving my project forward.

End

A step toward organizing information in the digital age

As the world moved toward everything digital, people had envision paperless for quite a while now.
To a large degree, for structured data, the world had made great stride. Databases and applications were created successfully to host those data and people everywhere are adopting those systems well.

The observation, however, is that for non-structured data, the adoption is somewhat of a slow processes in the making especially in the realm of organizing and using them.

For example, meeting notes, book notes, and class notes are a kind of un-structured data.


For the note taking industry, there is no shortage of note taking gadgets in the market, but most are just traditional note taking with gadgets.

In terms of organizing and using un-structured data, I would show two articles of interests:
  10 Ways to Improve How You Manage Information
    Which talked about how 'Information Management is a Hallmark of Better Productivity'
  Electronic Lab Notebooks
    where University of Cambridge is trying to help researcher to save/store their notes


At the University of Cambridge, they failed to recommend a single software for the University to adopt.

The meat of my suggestion is the use of a wiki-style system to organize notes or similarly un-structured data. Personally, I have used that systems for ages and, although not perfect, I found it is very useful.

Before I presented my wiki-style note system, let's step back and look at how people have been taking notes and how people have been organizing them.

In the cases of book notes or study notes, people/students wrote notes on papers with some kind of structure if they do choose. Once notes were taken, to organizing them, people can easily put related notes together in folders and filed into cabinet if they want by category or alphabetically.

In the cases of meeting notes or notes with similar natures, notes could be taken in similar fashion like the book note or study note, but the filing and organizing can certainly make differences. For example, a meeting may cover various topics/projects. In these cases, note taker may like to tear up the note so that he or she can file notes under the appropriate topic or project. However, if that is the case, this will tear-up the note of the meeting and it would be difficult to know the over all picture of the meeting.

The multi-topic nature of the meeting note isn't as unique as it may sound. For example, to file an article away, reader may notices that article covers two topics, like education and workforce. Filing the article under either the education folder or the workforce folder the reader risks the chance of finding that article the next time when he looking for it since he maybe looking in the wrong folder.


After reviewing few cases of how people dealing with paper notes, let's take a look at what a wiki system can do for us.

First of all, wiki is basically just a quick way to create linked web pages (read Wikipedia if you need to), where web pages are just like a Word document that you can type, you can highlight, and you can format, ...etc. The thing about wiki web pages, however, is that the linking is a second nature of wiki pages and creating a document is as easy as creating
a link.

When applying the wiki principle to the meeting note scenario, we could create, in each project page, a link to the meeting note page. In this way, all project page will aware of decisions made in that meeting while you have your meeting page intact. The other approach would be to cut and paste the meeting decision to each project page while create in the meeting page links that linked to each project page. In either case, you can always find those decisions no matter you follow the meeting page or the project page.

In the case of filing article away, you can easily create, in both the education page and the workforce page, links to the article page. In this way, you can always reach the article page no matter which way/page you choose.

When working on book notes or study notes, link can easily be created to a prerequisite knowledge page and can help the learning tremendously.

Filing or organizing information in wiki is great. But how about the presentation in terms of the 5 hats LATCH approach? In general, user can arrange pages in all five arrangements (Location, Alphabetically, Timeline, Category, and Hierarchically) manually at the same time since all we have are web pages and presentations would just be links to the pages. However, using selected approach for appropriate pages can make the presentation more logical.

Depend on implementation, some wiki system also handle pictures and files.


A retrospect:
Back to the time of folders and short file names, I would build folder hierarchy and try to store/organize files/information in a hierarchy way. With the short file name, I constantly have to create a text file: _ReadMe.txt to define and describe the content of the folder. With the introduction of Windows' 95, the _ReadMe.txt file can actually be a web page that provides links and description of the folder. With the shortcut of the file system, the folder web pages provide a fair information organization system. At the time, I did not try to see if it is possible to link folder pages. But, as you can see, the idea is very close to what I have today with the wiki web pages - Using web page with links to document/organize your information.

A project at Kickstarter.com:
Always-Organizer

CMS - a perspective

CMS, the content management system, may have all kinds of various names. But it is mean to organize the information.

After years of effort try to organize information, I came to a system that I think I would like to have at this point. I have to say this in a reserved way since people grow and there might be better way that I haven't envision yet.

There is no new idea here. I think all the features I am going to mention have exist in one system or the other and people may already have and using it. My intention is simply to point out my thoughts and it may benefit readers that haven't have their idea system yet.

I am envision a wiki like system with necessary securities and I think this idea can extended to file system of today's computer.


Personally, I think a lot of people are like me that kept document in computers, some at home and some at work. Personally I also have web spaces that I kept my notes.

For documents that I kept in computers, I organize them info folders and in each folder I would have a _ReadMe.txt file that describes things related to document in the current folder. In order to manage documents, I also use links if a document need to present in multiple folders based on the organizing logic.

On the web, I use a Wiki to keep my notes so that I can access from anywhere. This is important to me since I may come up with ideas at the work while it is not appropriate for the work by is totally OK for personal pursuit. Of cause, it can go the other way too. Therefore, it benefits not just the work but also personal life - Credit to my former boss, Steve Brown. He never prevent me from pursuing career outside my work place and he did mentioned that it benefits both.

One important feature of the Wiki is that it allows user to create linked page easily. It is, therefore, very easy to create a tree/graph like data structure. For example, I start the Wiki with ME as the beginning. I then create links to pages based on my roles - As a member of the family, as an employee of a company, as a citizen of a city, as a citizen of a state...etc. Each page can then link to other topics related to topic of the page. For example, under the citizen of a city, you can have link and note to, say, city government, legislature, TV stations, news papers ... etc.

Thinking the Wiki and my folder-organization in the computer, it occurs to me that the system I wanted is that of the Wiki with storage/upload - a lot of Wiki system do allow you to upload files - it just that I never enable the feature.

Thinking back, I remember there was a period of time, Windows is allowing user to create a html file in each folder and the html file will be opened by default when user navigated to that folder. As you can see this is almost idea to what I wanted if I spend enough time to build those html files - I am not sure if Windows still have this capability build in.

The other concept exhibits in this Wiki-storage system is that I really don't care where the upload file are stored - as long as I can access them via links.

So does the idea of folder obsolete? I think not. But I like to mention the idea of virtual or logical folder as existed in Hyland's OnBase product. The logical folder is created based on user's organization logic and not the physical location of the file in the file system. This made the logic folder a very good fit to the Wiki-storage system. As OnBase did, the content of the folder can be dynamically updated, based on criteria you set, as files are added to the organization system. For example, if you have a Wiki page that shows your personal music collection, it will be nice that when you add a file, it automatically show that new file. So, for Wiki-storage, this is a feature to be added.

As to the computer OS, the logical folder should be what most people wanted since most user really don't know or care where and how files are stored.