Desktops, metadata and filing: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 97: | Line 97: | ||
{{nld}} | {{nld}} | ||
{{sa}} | {{sa}} | ||
{{gb|[[Metadata]]<li>[[Excel]]<li>[[Dewey decimal system]]}} | |||
{{ref}} | |||
Revision as of 20:12, 23 September 2024
|
JC pontificates about technology
An occasional series.
|
A bad metaphor
In 1973, Xerox’s Palo Alto Research Center released the “Alto” personal computer. This was the first machine to boast a graphical user interface (GUI) instead of the traditional character user interface.[1]
To lessen the cognitive burden on users — at the time, bowler-hatted civil servants and sleeve-gartered clerks, whose mental framework was populated by mailboys running memoranda around the office in reusable envelopes, and whose idea of “information technology” was a pneumatic tube system that launched invoices around the organisation like mortar bombs — Xerox PARC’s designers created the metaphor of the “desktop”.
Yes, you were looking at a computer screen. But on that screen was not an impenetrable wall of green code following a flashing cursor, but a cartoonish depiction of a literal desktop, with manila folders, a blotter, filing cabinets, in-trays and out-trays and even a dinky little wastebasket. All very familiar.
A better metaphor
In 1979, Dan Bricklin and Bob Frankston created VisiCalc for the Apple II computer. VisiCalc was the first spreadsheet program, revolutionising computing by allowing even modest businesses easily to create and manipulate structured data.
VisiCalc wasn’t nearly quite as dinky or intuitive as the desktop. It didn’t need a graphic user interface. It was a much purer expression of what a personal computer could do, though: it promised a powerful means of storing, augmenting, filtering, analysing and manipulating structured data. It is, of course the ancestor to that beast we all now know and love as Microsoft Excel.
Why it’s is a good metaphor
Aspreadsheet is a much better way of thinking about how to organise information on a computer than is a desktop. Being a conceptually infinite number of rows and columns — limited in practice, but these days not by much — a spreadsheet extends in two infinite directions: downwards in that you can have any number of items in your filing system — each occupies a single row of a potentially infinite number of rows — and across in that you can categorise your list of items in as many different ways as your imagination affords, creating new columns for different categories, each of which may, but need not, be related to existing categories. If the columns you have, or a clever combination of them, don’t yield the information you need, you can always add more.
Each of these column categorisations are items of metadata — literally, “information about information” — about the item in the row. The metadata can be in the form of dates, checkboxes, people, colours, flags, choices, lookups, comments, or calculations. The data can be validated, controlled, compulsory and free-form. Each of extra piece of metadata enriches the existing data in the row without detracting from it.[2]
Each new piece of metadata is, in this way, “non-destructive” of the others. Each creates its own way of ordering the information. Each is its own hierarchy. Suddenly, you can organise the same information in multiple different ways at once. Without upsetting anyone else’s existing categorisation, which is still there.
You can then filter and group your items by one or more columns. You can sort, chart and triangulate them. The more metadata you have, the more ways you can look at the data. You can sort your data using data about how much metadata it has. This is metametadata.
The spreadsheet approach to file management is, thus “multi-hierarchical” and non-destructive.
The desktop clings on
Yet on our modern, hyper-networked, cloud-based work environment the desktop metaphor hangs on. We still call them “desktops”, though now for the prosaic reason that they generally are the only thing that sits on top of our desk. The desktop was a nice, quaint idea, and it got old men in green visors to sit down at a keyboard, and for that the ranks of middle management can be truly grateful, but it has well-outlived its purpose now.
Because physical information that sits on a real desktop, and digital information that sits on a computer are very different ontological propositions.
The desktop metaphor asks us to put our files in folders, as we would do on a real desk. If a folder gets too big, we create subfolders. And, just as with a real desk, once we have put a file in one folder, we can’t very well put it anywhere else. Just as with a real filing cabinet, if we misfile our subfolder, we might never find it again.
In the real world of physical information, that does no more than reflect grim corporeal reality: a thing can only be in one place at one time so that’s that. If the boss wants to file by customer, and you want to file by industry, then tough.
Physical filing systems reflect this: there is a unique physical location for any single document. So do physical filing methodologies: older readers may remember the Dewey decimal system, which numbered the entire corpus of non-fiction wisdom from zero to 1,000.[3]
If the same document does need to be categorised in different ways — say the legal department needs to file by customer and the credit department by industry, this could only be achieved by duplicating the document and holding one version in each location. Legal would have a filing system, and credit would have another.
Plainly, this is an imperfect state of affairs. It created a basis risk. Which was the canonical version of the document? What happened if one of them, but not the other, was updated?
In the physical realm, duplication was slow, imperfect and expensive and so, limited. At the time this seemed to be a drawback; with hindsight, it appears a valuable discipline.
Substrate neutrality
These are all problems problems of the physical realm; the spreadsheet metaphor shows us we need not be so troubled in a digital realm. In the digital world, the physical “substrate” of a document — the paper it is made out of — is, to all intents and purposes, irrelevant. What matters is the ASCII code embedded in that document. In a digital world it has been abstracted from the substrate and floats free. Within a diverse network of collaborators, this is immensely empowering.
It did not take people long to realise that email was amazing.
From, more or less, a standing start in about 1993 — by lucky coincidence the year JC entered the workforce — the corporate world fell head over heels in love with electronic communication. Whatever reverence it had for the sacred substrate fell quickly away.[4] The expression, “this document is not worth the paper it is written on” has lost its meaning because the paper it is written no longer has much value at all.
Now we recognise the digital content embedded in the substrate is the valuable bit; the paper bit is just annoying. It is an inconvenient reminder of our erstwhile physical analogue reality. The better metaphor than the “desktop” here is the spreadsheet. A spreadsheet is, of course a rudimentary form of a database.
In a spreadsheet that inconvenient imposition of substrate has gone: a “document” is nothing more that an information string: more or less costless to generate, transport, replicate and store. By simply appending metadata, we can enrich it and put the same thing in several places at once. We transcend the Euclidian geometry of physical space.
Now, I said our reverence it had for the sacred substrate fell quickly away. It did not entirely fall away. We still revere wet ink, for some reason counterparts clauses, and the dear old desktop. For still, as we file, we cannot resist the siren call of folders. Folders in folders in folders in folders in folders. Why do we persist with folders?
More than twenty years ago Tom Zingale taught a young JC a valuable lesson. Battling with some byzantine folder structure, and losing, Tom said this:
JC: How on earth am I meant to organise all this?
Tom: With metadata.
JC: Er, with what?
Tom: Metadata. The answer to your question is metadata. Metadata, metadata, metadata. Whatever your question is, the answer is metadata.
JC: Well, my question is, “How do I use metadata to fix this filing problem?
Tom: Oh, right. Simple: SharePoint.
About SharePoint
Now a lot of good people viscerally hate SharePoint. And, to be sure, Microsoft seems to have gone out of its way, over 20 years, to make SharePoint as hard to love as it can. But at the same time, it has based its entire Office 35 Suite on the SharePoint platform. It is, to be sure monumentally confusing, the Teams integration is baffling. The utterly dismal online versions of its Office suite drive people righteously up the wall.
But, still, a good part of the enmity for SharePoint arises from this fundamental misunderstanding. SharePoint is the first, philosophically, digitally native operating system.
SharePoint has abandoned the desktop metaphor.
SharePoint uses the spreadsheet metaphor.
In SharePoint you organise by metadata, not by folders.
DO NOT USE FOLDERS IN SHAREPOINT.
Folders are top-down. Metadata is bottom-up. Folders prefer form over substance. Metadata prefers substance over form.
Folders
Folders are very old economy. The folder metaphor is, literally, based on physical artefacts that can only be in one place at any time. If I put this item in the “Litigation” folder, I can’t also put it in the “Knowledge Management” folder.
Where the same unitary item deserves to be in both folders, I must therefore duplicate it. Where it is a “living thing” plotting its own miserable trajectory through the cosmos — a contract under negotiation, or a periodically updated legal template for example — then duplicating it is a bummer. It duplicates the manual task of updating all copies of the document as it changes, and that introduces the opportunity for human error. There may be miskeys. A document may be forgotten. Version control is a pain.
Also your preferred hierarchy can change, as personnel, business priorities, or circumstances change. Changing your hierarchy means completely re-engineering your folder structure.
So: a folder structure assumes a single hierarchy and multiple copies of each item.
Metadata
Metadata looks at the world the other way up. It says, “let there be a single canonical item, and multiple hierarchies.” Metadata allows you to non-destructively add hierarchies as you please. The more metadata fields you have, the more possible hierarchies there are. Unused hierarchies are almost costless.
Excel is a, well, excellent tool for managing metadata: Each row is an item and each column is a metadata point. You can add additional columns as you see fit without impacting what is already there: newly added columns are non-destructive as they augment without affecting existing ones.
In Excel you can filter sort and pivot by reference to any column in a table, in any order, and in doing so you impose a dynamic hierarchy on the items in the list. This is the magic of metadata.
SharePoint allows you to do exactly the same thing with a document library.
We intuitively understand the power of metadata when we are presented with a spreadsheet. But the same power does not occur to us when we are presented with SharePoint, even though it is, in essence, a supercharged online spreadsheet.
It is as if we take a preconceived notion of a physical library with us, and ignore our understanding of spreadsheets.
See also
References
- ↑ It was well ahead of its time: the GUI would not become mainstream until Apple released its Macintosh a decade later, in 1984.
- ↑ Indeed, even if the metadata is wrong, the inconsistencies between the fields allow a user to triangulate and identify likely wrong — or problematic — material
- ↑ My favourite was 001.9.
- ↑ I have a lengthy essay about the gradual extraction of data from the substrate but can't for the life of me find it at the moment.