Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Source-Based Defaults And Rules

IP.com Disclosure Number: IPCOM000028241D
Original Publication Date: 2004-May-05
Included in the Prior Art Database: 2004-May-05
Document File: 2 page(s) / 62K

Publishing Venue

IBM

Abstract

Disclosed is software for automatically setting environment and/or system defaults based on the source of the data. For example, the default directory to store e-mail attachments from John Doe is /JohnDoe.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Source-Based Defaults And Rules

Disclosed is software for automatically setting environment and/or system defaults based on the source of the data. For example, the default directory to store e-mail attachments from John Doe is /JohnDoe.

When a user has a file, or other form of data, typically he can opt to view, edit, save, or print. When a user has many types of files from many different sources, managing the files can be challenging. For example, Joe e-mails his boss, Sara, a report each week named "weeklyreport. txt". Sara wants to store all the reports on her local storage device. To do so, she must come up with her own layout. For example, she can create the following directories:

    /Apr-8-2004 /Apr-15-2004 Later, Jane starts sending a weekly report to Sara named "weeklyreport.txt". Sara can rework the original layout and create the following directories to accommodate the reports from Jane and Joe:

/Joe/Apr-15-2004 /Jane/Apr-15-2004

What is needed is software to help user's manage content based on the source of said content plus user configurable rules. For example, any e-mail attachments from sender Joe will automatically be stored in /Joe. A rule could be added that creates a $source+$timestamp directory, where $timestamp is the current time and date. For example, an attachment from Joe stored on Apr-15-2004 at 8:00:00AM EST would be created in /Joe/Apr-15-2004-8.00.00AMEST directory. An alternative rule could be $source+$filename+$timestamp. For example:

/Joe/weeklyreport.txt/Apr-8-2004-8.00.00AMEST /Joe/weeklyreport.txt/Apr-15-2004-8.00.00AMEST

An alternative rule could be $source+$monthYear+$filename+timestamp. For example:

/Joe/April2004/weeklyreport.txt/Apr-8-2004-8.00.00AMEST /Joe/April2004/weeklyreport.txt/Apr-15-2004-8.00.00AMEST

An alternative rule could be if $filename=="weeklyreport.txt": $source+$monthYear+$filename+timestamp; else $source+$timestamp. For example:

/Joe/April2004/weeklyreport.txt/Apr-8-2004-8.00.00AMEST /Joe/April2004/weeklyreport.txt/Apr-15-2004-8.00.00AMEST /Joe/Apr-12-2004-9.10.15AMEST /Joe/Apr-14-2004-10.02.10PMEST

By setting such defaults, the user gets the benefits of consistent layouts plus the user saves time from navigating said layouts. For example, Sara stores an e-mail attachment from Joe, Jane, then Joe again. Without the source-based scheme above, Sara would have to:
1) navigate up the directory tree to Joe's directory,
2) navigate down...