PIM Framework - Matjaž Kljun - Revision history

Mkljun at 22:33, 29 August 2010

2010-08-29T22:33:17Z

← Older revision		Revision as of 22:33, 29 August 2010
Line 3:		Line 3:
	''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''		''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''

	This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1. <ref name="kljun">Matjaž Kljun, Alan Dix and Franc Solina. A Study of a Crosstool Information Usage on Personal Computers: how users mentally link information relating to a task but residing in different applications and how importance and type of acquisition affect this. 2009</ref>		This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1. <ref name="kljun">Matjaž Kljun, Alan Dix and Franc Solina. A Study of a Crosstool Information Usage on Personal Computers: how users mentally link information relating to a task but residing in different applications and how importance and type of acquisition affect this. 2009 [http://eprints.lancs.ac.uk/33816/1/kljun-crosstool_information_usage_2009.pdf PDF]</ref>

	Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.		Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.

Mkljun at 22:27, 29 August 2010

2010-08-29T22:27:43Z

← Older revision		Revision as of 22:27, 29 August 2010
Line 3:		Line 3:
	''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''		''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''

	This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1. <ref name="kljun">Matjaž Kljun, A Study of a Crosstool Information Usage on Personal Computers: how users mentally link information relating to a task but residing in different applications and how importance and type of acquisition affect this, 2009</ref>		This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1. <ref name="kljun">Matjaž Kljun, Alan Dix and Franc Solina. A Study of a Crosstool Information Usage on Personal Computers: how users mentally link information relating to a task but residing in different applications and how importance and type of acquisition affect this. 2009</ref>

	Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.		Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.

Mkljun at 22:26, 29 August 2010

2010-08-29T22:26:18Z

← Older revision		Revision as of 22:26, 29 August 2010
Line 58:		Line 58:
	PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these		PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these
	overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).		overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).

			==References==
			<references />

Mkljun at 16:35, 2 August 2010

2010-08-02T16:35:57Z

← Older revision		Revision as of 16:35, 2 August 2010
Line 52:		Line 52:
	Both tasks include organizing. But first one is about moving piles of papers from a desk to make place for new ones and to support other future PIM activities (in the long run). While the second task is more about supporting present PIM activities (not get overflown with email on a daily bases). Certainly it also supports future PIM but is more focused in the present.		Both tasks include organizing. But first one is about moving piles of papers from a desk to make place for new ones and to support other future PIM activities (in the long run). While the second task is more about supporting present PIM activities (not get overflown with email on a daily bases). Certainly it also supports future PIM but is more focused in the present.

	'''Overlap and interchange'''		'''Overlap and interchange of PIM and other activities'''

	[[File:Kljun-pim-overlap.png\|thumb\|Figure 2: Overlapping and concurrent activities]]		[[File:Kljun-pim-overlap.png\|thumb\|Figure 2: Overlapping and concurrent activities]]

Mkljun at 16:35, 2 August 2010

2010-08-02T16:35:06Z

← Older revision		Revision as of 16:35, 2 August 2010
Line 3:		Line 3:
	''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''		''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''

	This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1.		This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1. <ref name="kljun">Matjaž Kljun, A Study of a Crosstool Information Usage on Personal Computers: how users mentally link information relating to a task but residing in different applications and how importance and type of acquisition affect this, 2009</ref>

	Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.		Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.

Mkljun at 11:47, 2 August 2010

2010-08-02T11:47:37Z

← Older revision		Revision as of 11:47, 2 August 2010
Line 53:		Line 53:

	'''Overlap and interchange'''		'''Overlap and interchange'''

			[[File:Kljun-pim-overlap.png\|thumb\|Figure 2: Overlapping and concurrent activities]]

	PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these		PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these
	overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).		overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).

	~~[[File:Kljun-pim-overlap.png\|\|Figure 2: Overlapping and concurrent activities]]~~

Mkljun at 11:46, 2 August 2010

2010-08-02T11:46:54Z

← Older revision		Revision as of 11:46, 2 August 2010
Line 57:		Line 57:
	overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).		overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).

	[[File:~~Kkljun~~-pim-overlap.png\|\|Figure 2: Overlapping and concurrent activities]]		[[File:Kljun-pim-overlap.png\|\|Figure 2: Overlapping and concurrent activities]]

Mkljun at 11:46, 2 August 2010

2010-08-02T11:46:26Z

← Older revision		Revision as of 11:46, 2 August 2010
Line 55:		Line 55:

	PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these		PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these
	8
	overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).		overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).

			[[File:Kkljun-pim-overlap.png\|\|Figure 2: Overlapping and concurrent activities]]

Mkljun at 11:41, 2 August 2010

2010-08-02T11:41:00Z

← Older revision		Revision as of 11:41, 2 August 2010
Line 1:		Line 1:
	~~==Matjaž Kljun==~~		[[File:Kljun-pim.png\|thumb\|Figure 1: PIM activities and activities outside PIM by Richard Boardman]]

	[[File:Kljun-pim.png\|thumb\|Figure 3: PIM activities and activities outside PIM by Richard Boardman]]

	''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''		''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''

	This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 3.		This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 1.

	Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.		Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.
Line 55:		Line 53:

	'''Overlap and interchange'''		'''Overlap and interchange'''

			PIM activities rarely take place one after another. More often PIM activities overlap with each other and other activities. Besides that performing some PIM activities can not be completed without involving organization (like manual acquisition), PIM activities can overlap because our needs overlap as well. While performing one activity a new activity can take place before the first activity ends as seen in Figure 2. For example while organizing emails (a present need), a need emerges such us ”I have to remind Bob of a meeting” (a pre-existing need we forgot about) or while browsing for a document in a file system (a present need) we come across MP3 files that trigger our need to listen to music (a new need). So needs for information can emerge during all PIM activities as well as needs for information are driving us to perform PIM activities. As described, these
			8
			overlapping PIM activities might not even be related to the management of the same information item(s) and run concurrently with other activities we perform in PSI (reading, editing, watching, listening, chatting ...).

Mkljun: /* Matjaž Kljun */

2010-08-02T11:36:28Z

Matjaž Kljun

← Older revision		Revision as of 11:36, 2 August 2010
Line 1:		Line 1:
	==Matjaž Kljun==		==Matjaž Kljun==

			[[File:Kljun-pim.png\|thumb\|Figure 3: PIM activities and activities outside PIM by Richard Boardman]]

	''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''		''Main article can be found [[PIM Framework - Matjaž Kljun\|here]]''

	This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between ~~these~~ activities; rather it presumes that ~~these~~ activities overlap (not only happen interchangeably).		This framework is based on [[Richard Boardman\|Bordman's]] and it includes four PIM sub-activities: '''acquiring''', '''organizing''', '''maintaining''' and '''retrieving'''. But it does not impose strict borders between PIM activities; rather '''it presumes that PIM activities overlap''' (not only happen interchangeably) as can be seen in Figure 3.

	Its starting point is on different acquisition types which influences all other activities. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.		Its starting point is on '''different acquisition types which influences all other activities'''. It tries to frame for example such issues: an email that is automatically acquired and placed in our inbox which is for example our personal information collection; is deleting this email a keeping activity as we process new email messages and decide which we will keep or discard; or is deleting maintaining as we decide which information stays in the collection.

	'''Acquisition'''		'''Acquisition'''

	Acquisition can happen in three different ways: '''created''', '''received''' and '''found'''. And each of these three sources can be acquired in several of these modes:		{\| border="0" cellpadding="10" cellspacing="0" align="center" width="95%" style="background-color: #eeeeee;"
			\|-----
			\| Acquisition can happen in three different ways: '''created''', '''received''' and '''found'''. And each of these three sources can be acquired in several of these modes:

	* Manually acquired information.		* Manually acquired information.
Line 16:		Line 20:

	We have a total control over manually acquired information which can be (re)named and/or placed in information environment based on our decisions at the time we decide. On the other hand, automatically acquired information piles up in a predefined place while we do not have a control over its acquisition. While semi-automatically acquired information still needs our action to be acquired but some actions (like naming and placing, time of acquisition) can be done without our intervention (e.g automatically by an application).		We have a total control over manually acquired information which can be (re)named and/or placed in information environment based on our decisions at the time we decide. On the other hand, automatically acquired information piles up in a predefined place while we do not have a control over its acquisition. While semi-automatically acquired information still needs our action to be acquired but some actions (like naming and placing, time of acquisition) can be done without our intervention (e.g automatically by an application).
			\|}

	Examples:		Examples:
Line 32:		Line 37:
	'''Organization'''		'''Organization'''

	Users change organizational structure (even if only a small part) also during other activities and that many such small changes incrementally (while thinking and rethinking about small portions of the existing schema) change structure and organization of PICs and PSI. As such information organization overlaps with all other activities as can be seen in Figure 3.		{\| border="0" cellpadding="10" cellspacing="0" align="center" width="95%" style="background-color: #eeeeee;"
			\|-----
			\| Users change organizational structure (even if only a small part) also during other activities and that many such small changes incrementally (while thinking and rethinking about small portions of the existing schema) change structure and organization of PICs and PSI. As such information organization overlaps with all other activities as can be seen in Figure 3.
			\|}

	'''Maintenance'''		'''Maintenance'''

	While organization deals with information items related to present ongoing tasks, maintenance is performed to support future (maybe unknown) needs and tasks. Maintaining means to manage the organizational schema in such a way that information related to past tasks, for which it is assessed that it will not be needed any more, is moved out of the way and the organizational schema is organized in a way to support future tasks while it still has to support ongoing tasks. Maintenance assures that organizational schema and existent information assist our needs and tasks in the longer run. Even here the border between maintenance and organization is not clear. During the maintenance users perform some organization activities (moving, deleting, creating folders and items, grouping, renaming, etc) and other activities such as archiving (moving out of sight either by moving information on removable media or hiding it deeper in a hierarchy), synchronizing and backing up.		{\| border="0" cellpadding="10" cellspacing="0" align="center" width="95%" style="background-color: #eeeeee;"
			\|-----
			\| While organization deals with information items related to present ongoing tasks, maintenance is performed to support future (maybe unknown) needs and tasks. Maintaining means to manage the organizational schema in such a way that information related to past tasks, for which it is assessed that it will not be needed any more, is moved out of the way and the organizational schema is organized in a way to support future tasks while it still has to support ongoing tasks. Maintenance assures that organizational schema and existent information assist our needs and tasks in the longer run. Even here the border between maintenance and organization is not clear. During the maintenance users perform some organization activities (moving, deleting, creating folders and items, grouping, renaming, etc) and other activities such as archiving (moving out of sight either by moving information on removable media or hiding it deeper in a hierarchy), synchronizing and backing up.
			\|}

	Consider two tasks:		Consider two tasks: