JP4481507B2 - Document management methods and tools - Google Patents

Description

【００６７】
表１に示されているように、ＸＭＬファイルは<PAGE>で始まり、</PAGE>で終了する。COMPONENT NAMEは、規定されたページの一部分に割り当てられた名前である。COMPONENT NAMEの例は、HEADER、TITLE、およびFOOTERである。<FILE>タグは、問題になっているＨＴＭＬテンプレートの位置を示すのに使用される。<TAG1>および<TAG2>はこの構成要素において使用されるタグである。既に記載したように、このようなタグのリストは例示的にテーブル１に記載した。<TAG1>YES</TAG1>は、呼出されているテンプレート内でTAG1が使用されることを示している。テンプレート内で使用される全てのタグはこのやり方で宣言される。
【００６８】
異なるタイプの機能を、例示的に<ARCHIVE>構成要素によって示す：
【表２】

【００６９】
<ARCHIVE>構成要素を含むと、内容ファイルがそれぞれのディレクトリ内に記憶されてから経過した時間が試験される。コンピュータファイルシステム内のファイルのメモリの日付および時刻は一般的に、関係するファイルの関係付けられた特性としてオペレーティングシステムから得られる。このようなアーカイブ構成要素を含むテンプレートを内容ファイルへ適用する際に、この時間期間が所定の時間よりも長いことが分かると、内容ファイルはアーカイブに入れられる。アーカイビングプロセスは後でさらに記載することにする。
【００７０】
図７に関して、これらのＸＭＬテンプレートはソースファイル構造700を介して記憶することができる。しかしながらこの実施形態の実行を示すことによって、たった１つのサブディレクトリ内のこのようなＸＭＬテンプレートの配置をここで詳しく記載する。しかしながら類似のＸＭＬテンプレートはソースファイル構造700を介して望まれているようにシードされることが分かるであろう。第３の２番目の層のサブディレクトリ708は、第１および第２のＸＭＬテンプレート718、720を記憶しているように示される。第１のＸＭＬテンプレート718の機能は、上述にしたがってＨＴＭＬテンプレートのアセンブリを示すウエブページとして内容ファイルの外観を規定することである。第２のＸＭＬテンプレート720の若干異なる機能は、後で記載されるように、他のウエブページへのリンクを含むディレクトリページの内容の生成を可能にすることである。
【００７１】
第１および第２の実施形態に関係して論述した観点にたつと、第１のＸＭＬテンプレート718は階層形ソースファイル構造700を下方向に‘継承’されるといわれている。この‘継承’アプリケーションの効果は後でより詳しく記載することにする。
【００７２】
段階608では、ツールの動作に有益な大域情報（グローバルインフォメーション）を含むファイルを生成できる。したがってＸＭＬ内に書込まれた制御ファイル722は別個のディレクトリ714へ記憶される。
【００７３】
例えばＸＭＬ内に書込まれた、アーカイブページの外観を判断するように機能するアーカイブファイル726も生成され、別個のディレクトリ714内に記憶される。制御ファイル722内に記憶された大域情報は、例えば、このアーカイブテンプレート726のメモリの位置にあってもよい。
【００７４】
段階610では、階層形ソースファイル構造700を介して内容ファイルを紹介する。ここでも例示的に、テキストファイル（ファイルの拡張、'.txt'）724が第３の２番目の層のサブディレクトリ708内に記憶されているように示されている。さらにここでも、このようなファイルは、望み通りにソースファイル構造700を介して記憶されると理解される。ここでもウインドウズ（Windows, 商標）オペレーティングシステムを使用するとき、例えばウインドウズファイルマネージャ（Windows File Manager, 商標）またはウインドウズエクスプローラ（Windows Explorer, 商標）を使用して、ファイルを記憶できることがよく知られている。
【００７５】
段階612ではツールの呼出しを行う。
【００７６】
ここでツールの動作を図３、７、および８をさらに参照して記載することにする。
【００７７】
一般的にツールは、呼出されると、少なくとも３つのパラメータ：すなわちコンピュータファイルシステム（この例では別個のディレクトリ714）内における制御ファイルの位置、コンピュータシステムファイル内におけるソースファイルの位置（この場合はソースファイル構造700の位置）、および‘テンプレートで処理された’ウエブページが出力される‘目標（ターゲット）’ディレクトリの位置を送られる。
【００７８】
第１および第２の実施形態に関して、ソースファイル構造700の位置が与えられると、呼出されたときに、ツールは最初にいわゆる‘ツリー横断’手続きをトップダウン方式で実行することになる。さらにここでも第１の手続きの途中で、ルートディレクトリおよびサブディレクトリに関するファイル構造の分岐形態がツールによって検出され、記憶される。ここでも、既に記載したように、一般的にツールによって記憶された分岐形態の記述は、所与のディレクトリの名前、所与のディレクトリの親ディレクトリの関係性および名前、所与のディレクトリのサブディレクトリの関係性および名前、所与のディレクトリと同じ親ディレクトリを共有している他のディレクトリの関係性および名前、などに関する情報を含む。
【００７９】
第１の実施形態と同じように、ツールは次にボトムアップ方式でツリー横断手続きを実行する。この第２の手続きは第1の実施形態に関して記載した手続きと類似しており、ここでは図３に示したプロセスフローチャートに関して記載することにする。
【００８０】
上述から明らかなように、この第３の実施形態で使用されるテンプレートは、第１および第２の実施形態に関して記載されたテンプレート自体がフラグメントのテンプレートからアセンブルされたテンプレートとは異なる。したがって段階302に等しいとして、ツールは第1の実施形態の観点のテンプレートではなく、第１のＸＭＬテンプレート718をサーチする。このテンプレートは、段階304に相当してツールによって適用されるとき、関連するＨＴＭＬテンプレート716を呼出して、内容ファイル724に適用される特定の構成されたテンプレートをアセンブルする。
【００８１】
本発明者の前記審査中の出願に記載された方法にしたがって、テキストが記載されている内容ファイル724を使用して、ＨＴＭＬファイルを生成する。しかしながら、これを実行する際に、本発明の第３の実施形態にしたがって、ＨＴＭＬテンプレートをアセンブルしたＸＭＬテンプレートも適用され、新しい‘テンプレートで処理された’ファイルはウエブページとして使用するのに適したＨＴＭＬの形態を有するのみでなく、例えばテンプレートにしたがって所望の外観を有している。このやり方で内容ファイルは‘テンプレートで処理された’ウエブページへ変換さる。
【００８２】
外部のオーサによって提出されたテキストが記載されている内容ファイル724がＨＴＭＬステートメントを含むとすると、これらのＨＴＭＬステートメントは、本発明のこの実施形態にしたがって、テンプレート用ＨＴＭＬと衝突しない範囲で敬意を表される（条件を充当する）ことに注意すべきである。１つの例では、内容ファイルのテキスト本体内にハイパーリンクを含んでもよい。最初の２つの実施形態に関して、新しいファイルは当然、どこに記憶してもよい。
【００８３】
しかしながらその代わりに、この第３の実施形態において、ツールは呼出しの際にツールに対して特定された位置において‘目標’ファイル構造を生成し、ツールによって生成された新しくテンプレートで処理されたファイルはこの‘目標’ファイル構造へ出力される。目標ファイルディレクトリの構造は、ソースファイル構造を鏡映する。図７に示しされ、図８に関係するソースファイル構造の例を使用して、鏡映された目標ファイル構造800を生成する。1番目の層のルートディレクトリ802は、第１、第２、第３の２番目の層のサブディレクトリ804、806、808と、第１および第２の３番目の層のサブディレクトリ810、812、とを有し、図７に対応付けて示されている。ソースファイル構造700の第３の２番目の層のサブディレクトリ708内の内容ファイル724に対応する新しく‘テンプレートで処理された’ファイル814は、目標ファイル構造800の第３の２番目の層のサブディレクトリ808内に記憶される。
【００８４】
既に記載したように、第１および第２のＸＭＬテンプレート718、720の両者の形態をとるテンプレートおよび所望の内容ファイルは、ソースファイル構造700においてシード（seed）されることが分かる。
【００８５】
上述の方法は、ソースファイル構造700内に記憶された各内容ファイルに対して実行される。関係するテンプレート、すなわち第1のＸＭＬテンプレート718に対応するテンプレートは各内容ファイルに適用され、対応するテンプレートで処理されたＨＴＭＬファイルは、ウエブページとして使用するのに適しており、目標ファイル構造の適切な（サブ）ディレクトリへ出力される。
【００８６】
第２のＸＭＬテンプレート720およびそれに相当するものは、ツールによって適用され、分岐形態のツールによって記憶されたソースファイル構造700の記述を使用して、目標ファイル構造の各（サブ）ディレクトリに対してディレクトリの文書を生成する。図８に関して、ディレクトリ文書816は、ウエブページとして使用するのに適したＨＴＭＬファイルの形態で生成され、例示的に、第３の２番目の層のサブディレクトリ808内に記憶されているように示されている。このディレクトリページ816内に含まれているＨＴＭＬの命令によって、リンクが用意され、例えばこの（サブ）ディレクトリ内の全ての‘テンプレートで処理された’内容が記載されているウエブページへのアクセスを許可するだけでなく、例えばホームまたはルートディレクトリ、親ディレクトリ、子（サブ）ディレクトリ、および（同じ親ディレクトリを共有している）同胞（sibling）ディレクトリ、または別の例では、アーカイブページをナビゲートする。
【００８７】
ディレクトリページ内の‘アーカイブ’リンクはアーカイブページへ導かれ、例えば、関連のディレクトリページと同じ（サブ）ディレクトリ内に生成され、記憶される。アーカイブプロセスの上述の記述にしたがって、ＸＭＬテンプレート内にアーカイビングタグを含むとき、そのテンプレートを、所定の時間期間よりも前に記憶された内容ファイルへ適用する際に、その内容ファイルは‘アーカイブされた’ファイルであると考えられることになる。内容ファイルは依然として‘テンプレートで処理された’ウエブページを生成するのに使用されるが、エントリは関連する（サブ）ディレクトリにおける‘現在の’ディレクトリページ内に現れず、むしろディレクトリページが上述のアーカイブページへのリンクを含み、このリンクが‘アーカイブされた’‘テンプレートで処理された’ウエブページへのリンクを用意する。図８に関連して、例示されたアーカイブページ818は、再び第３の２番目の層のサブディレクトリ808内に記憶されているように示されている。
【００８８】
よく知られているように、目標ディレクトリ内に記憶されるウエブページをウエブサイトとして使用可能にするために、コンピュータファイルシステム内の目標ディレクトリの位置を単に、ウエブサーバアプリケーションプログラムに用意してもよい。適切なウエブサーバアプリケーションプログラムの１例には、Microsoft Internet Information Server(商標)がある。次にウエブサーバは、ウエブサイトを適切な接続上の外部のウエブブラウザへアクセス可能にする。
【００８９】
上述から本発明の方法およびツールの第３の実施形態では、ウエブサイト生成についての効果的な手段を提供することが明らかである。
【００９０】
本発明者の前記審査中の国際特許出願において詳細に記載されているように、‘管理される’ウエブサイトは、従来技術に関係する付随的な問題に関してではなく、単に、（例えば、異なるタイプのミーティングに関係する）適切な形態のソースファイル構造を生成し、テンプレートの構造全体で（この例では、異なるタイプのミーティングに関係して、下方向に‘カスケードとなっていて’、より一般的なミーティングテンプレートは、さらに特定されたテンプレートによって用意された範囲まで相補またはオーバーライドして）シードし、（この例では、各異なるタイプのミーティングと関係付けられた）関係する文書の適切なディレクトリ内に記憶し、最後に（ツールを動作する）方法を実行することによって生成できることが明らかである。
【００９１】
しかしながらこの上、本発明の方法およびツールの第３の実施形態は、既存のソースファイル構造を再び実行する簡単な手段によってウエブサイトの効果的なメンテナンス手段も提供することが分かるであろう。
【００９２】
既存のウエブサイトの‘ルックアンドフィール（look and feel）’が変更するとき、非常に簡単に、別々のディレクトリ内に記憶されたＨＴＭＬテンプレートが編集されて、再び実行される。次にウエブサイトは、新しい‘ルックアンドフィール’を規定する新しいＨＴＭＬテンプレートを使用して、再び生成される。さらに、既存のＸＭＬテンプレートが異なるディレクトリへ移動されるか、または新しいテンプレートがソースファイル階層構造の適切なディレクトリへ導かれて、所望の経路および再実行されたツール内のテンプレートのカスケードを変更する。
【００９３】
多様な寄与しているオーサからの新しい内容ファイルは、もちろんソースファイル構造の適切なディレクトリおよび再実行されたツールへ導かれ、新しいない様ファイルが所望の‘ルックアンドフィール’をもつウエブページにし、既存のページとの一貫性を達成することができる。
【００９４】
従来技術では、ウエブサイトの再構成が実行されるとき、一般的に相互接続されたハイパーリンクの手入力の修正が要求される。よく知られているように、手入力の処理は、ハイパーリンクが指示している文書が最早その位置に存在しないときに、しばしばいわゆる‘ブロークンリンク（broken link）’になる。
【００９５】
本発明の第３の実施形態で再構成（リストラクチャリング）が要求されるときは、ソースファイル構造を修正し、文書およびテンプレートを近くに移動して、所望の再構成を行っても、ツールが再実行されるたびに、生成されたウエブサイトは新しく再生成されるので、このようなリンクの破壊は発生しない。
【００９６】
さらに、ツールが実行されるたびにアーカイビングプロセスを行って、より古い内容をアーカイブして、それでも確実にアクセスできることを自動的に保証することができる。
【００９７】
よく知られているように、このようなツールの再実行は、例えば毎日スケジュールされたイベントとして行われ、本発明にしたがってウエブサイトの持続的で効果的な管理を行うことができる。
【図面の簡単な説明】
【図１】 汎用コンピュータシステムを示す図。
【図２】 第1のソースファイル構造と、その中に記憶された関係付けられた内容およびテンプレートファイルとを示す図。
【図３】 第１のソースファイル構造と、その中に記憶された関係付けられた内容およびテンプレートファイルに関して使用する第1のプロセスのフローチャート。
【図４】 第２のソースファイル構造と、別個のディレクトリと、その中に記憶された関係する内容およびテンプレートファイルとを示す図。
【図５】 第２のソースファイル構造と、別個のディレクトリと、その中に記憶された関係付けられた内容およびテンプレートファイルとに関して使用するための第２のプロセスのフローチャート。
【図６】 別個のディレクトリを有する第３のソースファイル構造を設定し、かつその中に関係付けられた内容およびテンプレートファイルを記憶するための第３のプロセスのフローチャート。
【図７】 図６のプロセスのフローチャートにしたがって設定された第３のソースファイル構造と、その中に関係付けられた内容およびテンプレートファイルを記憶している別個のディレクトリとを示す図。
【図８】 図７に示したように、ソースファイル構造と、関係付けられた内容およびテンプレートファイルとから生成された目標のファイル構造を示す図。[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a document management method stored in a computer file system. The invention further relates to a tool for managing documents stored in a computer file system.
[0002]
Conventional technology
It is well known that the storage and retrieval of information by a computer is facilitated by using a computer file storage system. See, for example, the literature by Tanenbaum and Woodhull ('Operating Systems, Design and Implementation', Prentice Hall 1997). When used on a computer configuration such as a file memory system, an application program such as a word processor can store and retrieve electronic documents using, for example, a computer.
[0003]
As is more well known, the requirement to allow computer users to share access to electronic documents using a shared computer file memory system is accomplished by linking the computer to the appropriate network. The Next, a shared computer file memory system is used to construct a collaborative document memory where multiple collaborative authors have access to stored collaborative (centralized) work. Can be shared.
[0004]
With respect to traditional printed documents, electronic documents of various purposes are naturally led to the various styles in which these documents appear. In terms of sophistication, word processing applications can be freely selected in terms of document display style from a very simple text editor that handles only ASCII (American Standard Code for Information Interchange). Gives a range of complex desktop publishing packages.
[0005]
In many cases it has been found desirable to control the appearance of the document using so-called 'templates'. When creating a document, a template is selected, and the contents of the document, such as text, are generated within the template. A default template may be provided by the word processing system. However, if a different template is desired according to the user's choices or needs, this must be selected manually. In any case, the features of the template are specified by the instructions in the document that are intended to be applied, and thus the document itself will be linked so that it cannot be solved.
[0006]
Thus, one problem faced by word processing system users is that the next time another template is desired to be applied, the new document is opened with the new template and the contents of the old document are copied to the new document. That must be pasted. Furthermore, when such changes are required for a batch of documents, each document must be changed individually.
[0007]
A related problem faced by administrators of computer file systems that make up collaborative document memories is that each collaborative author has different personal preferences for different word processing systems or document styles. . In this way, the different documents supplied to the memory have different appearances, in which case the collaborative document memory will lack a consistent (consistent) 'look and feel'. In order to construct such a consistent 'look and feel', it is necessary to manually apply the desired template to each document, as already described.
[0008]
At present, such a collaborative document memory exists very appropriately as a 'website'. It is well known that the World Wide Web (hereinafter referred to as WWW or Web) has a great variety of related concepts and standards. A well-known example of a rich source of information related to these concepts and standards is the World Wide Web Consortium (http://www.w3c.org), an organization responsible for the development of such standards. is there. The World Wide Web Consortium is centered on the Massachusetts Institute of Technology (MIT) at the Massachusetts Institute of Technology (MIT). Concepts such as 'Website', 'Webpage', 'Web Browser', 'Hyperlink', and standards such as HyperText Markup Language (HTML) and eXtensible Markup Language (XML) are standard Generalized Markup Languages. It will be well understood as an example of (SGML).
[0009]
The problem of creating a consistent website 'look and feel' was addressed, for example, by the development of so-called 'Cascading Style Sheets (CSS). CSS provides a range of 'inheritance' in style features, and such features can be 'cascaded' through related documents. However, for today's example above, the style features will be identified or invoked by instructions in the document that are intended to be applied, and will again be linked so that they cannot be distinguished from the document itself.
[0010]
While far away from the issue of hierarchical control of the appearance of pages within a website, a more general problem with website management is that there is no resulting 'hyperlink break' in the web page. It is known to include management of the content being represented, such as archiving content that is older than a predetermined number of days.
[0011]
Problems to be solved by the invention
According to one aspect of the present invention, a method for managing content bearing information stored in a computer file system that is divided into directories:
Locating content files, each stored in a directory of a computer file system;
Associating a template file with each directory in which at least one content file is stored; each template file becomes effective when applied to the content file and performs a respective predetermined operation on the content file;
Applying the or each template associated with a given directory to each content file stored in that directory.
[0012]
In this manner, it is advantageous to associate the template file with the directory in which the content file is stored, rather than with a specific content file as in the prior art. Thus, the template selected for application to a given content file is related to the directory where the content file is stored and the selected template, or the selected template is related. You can select a content file by moving it to a directory. So, if it is desired to apply a different template, instead of manually re-editing the 'processed with the template' file generated in a way that was necessary in the prior art, it is quite easy to create a different template. Either the content file is associated with the stored directory, or the new template is moved to a different directory with which it is associated, and in either case, the method is performed again.
[0013]
It will be appreciated that this method is even more convenient when a batch of files has a new template applied. A new template can be associated with the directory where the batch of files is stored, or the file of the batch can be stored within the directory with which the new template is associated. In any case, the need to manually re-edit each content file and all content files can be avoided here.
[0014]
The computer file system is divided into hierarchical directories; and there is a directory that contains content files up to and including the top directory in the hierarchical structure, from which Preferably, a template that is placed in the direct hierarchical path and associated with each directory is also associated with the directory in which the content file is stored.
[0015]
Advantageously, several templates can be applied hierarchically to a given content file in such a way as to allow cascading of template styles. A consistent 'look and feel' in this manner can generate a display of content files stored in a hierarchical file system. Again, the template is applied to the content file and the template that realizes this advantage (advantage) is applied simply by associating with the directory where the content file is stored. Changes in the cascading style (style cascading) relate the desired template to a given hierarchical path, or not by tedious manual re-editing of each and all content files This can be done very easily by taking the move of the file to a directory in the appropriate hierarchical path.
[0016]
More preferably, the template is associated with the directory based on storing the template file in the directory.
[0017]
This not only provides a particularly simple and elegant means of associating templates with directories, but it is also convenient to further identify unwanted associations. All of the relationship information required by the present invention is provided by a simple selection of the template location.
[0018]
This method further:
Associating metadata with each content file;
More preferably, when applying the related template file based on each related metadata, each predetermined operation is performed on each content file.
[0019]
This method advantageously allows the template to perform various file management operations on the content file according to metadata information about the content file. One simple example relates to the time elapsed (metadata item) since the content file was stored in the directory; when a template is applied, the metadata is stored in the directory. When a time longer than a predetermined time has passed, the contents file is executed to be archived.
[0020]
An apparatus for performing the method is also provided.
[0021]
Embodiments of the present invention will now be described by way of example with reference to the accompanying drawings.
[0022]
BEST MODE FOR CARRYING OUT THE INVENTION
A first embodiment of a method and tool according to the present invention will now be described with reference to FIGS.
[0023]
FIG. 1 shows a typical general purpose computer 100. Such a computer 100 generally includes at least a central processing unit (CPU) (not shown), a read-only memory (ROM) (not shown), a random access memory (not shown). random-access memory (RAM) (not shown), a memory device such as a hard disk (not shown), a memory medium such as a floppy disk drive 102 for reading from and writing to the floppy disk 104, Devices for reading and writing, input devices such as keyboard 106, display devices such as mouse 108, monitor 110, input and output ports for connection to other devices or communication networks (not shown) Have In FIG. 1, a computer 100 is connected to a communication network 112 so that the communication network 112 can communicate with other computers 114, 116, 118 that are similarly connected.
[0024]
The computer 100 uses an appropriate operating system, and Microsoft Windows (trademark) is well known as an example of such an operating system. Application programs are appropriate and can be written in language. Such operating systems and application programs can be loaded into a memory device (not shown) of the computer 100. The application can be written in Java (trademark), for example, and in this case, the Java virtual machine needs to exist on the computer 100. As is well known, a Java virtual machine can be used to download from the Sun Corporation ™ website (http://www.sun.com). There are many well-known options for languages suitable for writing application programs, such as C ++.
[0025]
The tool described according to the first embodiment of the present invention is configured as a software application program executed by the computer 100. Tools configured as software application programs are stored, for example, on a floppy disk 104 in a suitable computer readable memory medium via a floppy disk drive 102 for loading into a computer for execution. A well known alternative tool is to run a software application on a CD-ROM (not shown) via a CD-ROM drive (not shown) for loading into the computer 100 for execution. You may remember. Yet another well known tool downloads a software application program over the network 112 for execution by the computer 100.
[0026]
Before the tool is called, the file system and the file on which the tool is executed must be prepared. Referring to FIG. 2, a two layer hierarchical file structure 200 is shown, which includes a first layer root directory 202 and first, second and third second layer subdirectories 204, 206, 208. The first text document 210 is stored in the root directory 202 of the first layer, and the second, third, and fourth text documents 212, 214, and 216 are the first, second, and third second, respectively. Stored in the layer subdirectories 204, 206, 208. The first template file 218 is stored in the root directory 202 of the first layer. The second template file 220 is stored in the first second layer subdirectory 204.
[0027]
When invoked, the tool first performs a conventional 'tree traversing' procedure on the hierarchical file structure 200 in a top-down manner. 'Tree crossing' is also known as 'tree creeping' or 'tree crawling'. As is well known, during this initial procedure, the branching form of the file structure 200 with respect to the root directory 202 and subdirectories 204, 206, 208 is detected and stored by the tool. In general, branching descriptions stored by tools include the given directory name, the relationship and name of the parent directory of the given directory, the relationship and name of the subdirectories of the given directory, the given directory and It may include relationships and names of other directories shared with the same directory, etc.
[0028]
The tool then performs the tree traversal procedure bottom up. This second procedure will be described with respect to the process flowchart shown in FIG. This process is performed for each content file stored in the file structure 200.
[0029]
In step 300, one particular content file is selected that is stored in a given subdirectory. In step 302, the tool first searches the subdirectory where the content file itself is located relative to the template file. If such a template file is found, the tool applies the template to the content file according to step 304 and ends the process for that particular content file.
[0030]
In general, applying a template to a content file in this way involves first opening a new file containing the template. The body of the content file is then automatically copied and pasted into this new file. In this way, the template is automatically applied to the body of the content file based on where the content file is stored. In practice, the template is associated not only with the content file itself as in the prior art, but with the (sub) directory where the content file is located. The new files may of course be stored anywhere, but by way of example FIG. 2 shows new (processed with template) files 222, 224, 226, 228 (in dotted lines) that are templates. Stored in the same (sub) directory as the content file based on the processed file.
[0031]
However, if such a template is not found in the subdirectory, then according to step 306, unless the (sub) directory is not the root directory, then according to step 308, the tool will return the parent of the subdirectory where the content file is located. Consider (sub) directories. If no such template is still detected when repeating step 302, steps 306, 308, and 302 are further repeated to continue searching the hierarchical structure until a template is detected. This template is then applied. If the template is not searched in the root directory, the process for this particular content file ends.
[0032]
It will be appreciated that the process flowchart shown in FIG. 3 shows an exclusive application of the template. If a single template is found, this template is applied. It will further be appreciated, however, that the templates are applied in conjunction with each other, either being complementary to each other or overriding each other in the range provided. In this case, bottom-up tree traversal is a complete traversal of the tree from the lowest subdirectory under consideration to the root directory, determining the location of all relevant template files and ensuring that all relevant templates are appropriate. A simple application.
[0033]
In particular, with respect to FIGS. 2 and 3, instead of placing a template 220 in the first second tier subdirectory 204, the tree traversal ends according to step 304, but the template 220 And continue to record the position of the first template 218 in the root directory 200 up the hierarchy. The appropriate application for both the first template 218 and the second template 220 can then be executed.
[0034]
In this way, it will be clearly seen that in this example the template is 'inherited' down the hierarchy from the parent directory to the child directory, and performs template style 'cascading'. With reference to FIG. 2, the first template 218 is applied to the first, third, and fourth text documents 210, 214, 216. However, both the first template 218 and the second template 220 are applied to the second text document 212.
[0035]
Illustratively, the first template 218 is suitable for use with documents in the first tier root directory 202 and the second and third second tier root directories 206, 208. The second template 220 defines a template for a specific meeting, for example a board meeting, which compensates to the extent that the general meeting template is given by the board meeting template. Or request to be overridden.
[0036]
It will be readily apparent that the first embodiment of the present invention represents a significant technical advantage in accordance with the prior art.
[0037]
For example, when another specific meeting type is generated and a third template is requested and the related document is stored in the second second tier subdirectory 206, the third template is all associated. All that is required to apply to the document is to store the third template in the second second tier subdirectory 206 and rerun the tool to perform the method again.
[0038]
By another example, a batch of documents, such as the fourth text document 216 stored in the third second tier subdirectory 208, was processed with a template suitable for use in a board meeting. When required to change to a form, move all relevant document files from the third second tier subdirectory 208 to the first second tier subdirectory 204 in this example. All that is required is to achieve and then re-run this method.
[0039]
A second embodiment according to the present invention will now be described with reference to FIGS.
[0040]
With reference to FIG. 1, the tool disclosed by the second embodiment of the present invention may again be configured as a software application program executed by the computer 100. Tools configured as software application programs are stored on, for example, a floppy 104 or CD-ROM (not shown) for loading into the computer 100 for execution in the form of a suitable computer-readable memory medium. Also good. Again, in a well-known alternative example, a software application program is downloaded over the network 112 for execution by the computer 100.
[0041]
Again, by way of example, a two layer hierarchical file structure 400 has a first layer root directory 402 and first, second, and third second layer subdirectories 404, 406, 408. It has been shown that Again, the first text document 410 is placed in the root directory 402 of the first layer, and the fourth, fourth, and fourth text documents 412, 414, and 416 are the first, second, and third, respectively. In the second tier sub-directory 404, 406, 408.
[0042]
In a separate directory 418, a lookup table 420 is stored outside the hierarchical file structure 400. First and second template files 422, 424 are also stored in separate directories 418. Lookup table 420 associates (sub) directories with templates. In this example, the lookup table associates the first template file 422 with the first layer root directory 402 and the second template file 424 with the first second layer subdirectory 404. It is shown that. It will be appreciated that a lookup table is just one example of providing a correspondence between a (sub) directory and a template. Other examples such as linked lists are well known.
[0043]
With respect to the first embodiment, the tool, when invoked, performs a 'tree traversal' procedure in a top-down manner. Again, during the first procedure, the branching form of the file structure 400 is detected for the root directory 402 and subdirectories 404, 406, 408 and stored by the tool. Again, the branching description generally stored by the tool is the name of the given directory, the relationship and name of the parent directory of the given directory, the relationship and name of the subdirectory of the given directory , Information on the relationships and names of other directories that share the same parent directory as a given directory, the names of files stored in a given directory, and the like.
[0044]
The tool then performs a tree traversal procedure in a bottom-up manner. This second procedure will now be described with respect to the process flowchart shown in FIG.
[0045]
In step 500, a particular content file stored in a given subdirectory is selected. In calling the tool, at step 502, the tool first looks up the lookup table 420 to see if there is a template file associated with the subdirectory where the content file itself is located. If such a template is detected, the tool applies the template to the content file according to step 504 and the process for this particular content file ends.
[0046]
Again, in general, applying such a template to a content file involves opening a new file containing the template. The body of the content file is automatically copied and pasted into a new file. In this way, the template is automatically applied to the body of the content file. The new file can of course be stored anywhere, but here again by way of example, the new 'template processed' files 426, 428, 430, 432 are shown in FIG. Are shown to be stored in the same (sub) directory based on the modified file.
[0047]
However, if it turns out that such a template is associated with a subdirectory, then according to step 506, unless this (sub) directory is the root directory, the tool looks up the lookup table 420 according to step 508 and the content file is Find out if there is a template associated with the parent subdirectory of the subdirectory in which it resides. If such a template is still not found when repeating step 502, the tool continues to search the hierarchy until such a template is detected by repeating steps 506, 508, and 502. The template is then applied. If no such template is found and associated with the root directory 402, the process for the particular content file ends.
[0048]
Again, consider a non-exclusive application of templates for the first embodiment. 4 and 5, in this alternative application, once the template associated with the first second tier subdirectory 404 is located, the tree traversal does not end according to step 504, but this template 424 , And continue to record the relationship of the first template 422 in the root directory 402 up the hierarchy. Appropriate applications of both the first template 422 and the second template 424 can be executed.
[0049]
In this way, the template is again “inherited” down from the parent directory to the child directory, giving the template style 'cascading' and the related advantages described for the first embodiment.
[0050]
A third embodiment of the present invention will now be described with reference to FIGS. 1, 3, 6, 7, and 8.
[0051]
Referring to FIG. 1, the tool disclosed according to the third embodiment of the present invention may again be configured as a software application program executed by the computer 100. A tool configured as a software application program, for example, in the form of a suitable computer readable memory medium for loading into the computer 100 for execution again, such as a floppy disk 104 or CD-ROM (not shown). Not) may be stored on. A well-known alternative here is to download a software application program over the network 112 for execution by the computer 100.
[0052]
The subject matter of International Patent Application No. PCT / GB98 / 00804 which is being examined by the inventor is also incorporated herein by reference.
[0053]
The method described in this pending application uses a simple document, eg a text document, to represent the content of a simple document, eg an HTML document, and derive a suitable one for use on a website. be able to. Files containing the desired 'content' obtained in the web page are placed in directories and subdirectories of the file structure. When this method is invoked, this file structure is traversed and then the content file stored in the file structure is used to generate a web page representing the relevant 'content'.
[0054]
The methods and tools described herein as the third embodiment of the present invention enhance the functionality of the methods described in the pending application. Files containing template information are placed in a separate directory outside the file structure. However, yet another file containing template information is placed in directories and subdirectories of the file structure. When an 'enhanced' tool (hereinafter referred to as 'tool') according to the third embodiment of the invention is called, the appropriate template is assembled and contains a file, eg a text document Generate web pages that are applied to their content and are 'managed' through the application of these templates.
[0055]
FIG. 6 shows a flowchart displaying the process by which such a 'managed' website is created using the tool. Each stage 600-612 is further illustrated with reference to FIG. It will be appreciated that the order of some of the stages shown in FIG. 6 can be interchanged since many of these stages include independent settings to replace the elements that work when the tool is invoked.
[0056]
Step 600 generates the 'source' file structure that the tool will work on later. FIG. 7 shows an example of a source file structure 700 having a three-layer hierarchical structure. The first tier root directory 702 is created with the first, second, and third subdirectories 704, 706, 708 at the second tier level. When the first and second subdirectories 710, 712 are created as subdirectories of the third second tier subdirectory 708, they are provided to the third tier level. It is well known that this can be accomplished when using the Windows operating system, for example using the Windows File Manager (trademark) or Windows Explorer (trademark).
[0057]
Step 602 generates a set of HTML templates in this exemplary embodiment. However, it will be appreciated that other suitable forms of templates can be used.
[0058]
As is well known, web 'pages' can be generated using a specific markup language, namely HyperText Markup Language (HTML). The text or graphic appearance of a given web page can be controlled along with the linking between web pages. HTML instructions are also known as 'tags'. Therefore, the format of the web page can be defined by inserting an HTML tag in an ASCII text document, for example. A variety of simple text editors, word processors, and more advanced HTML editors can be used for this purpose. One example of a suitable application program is Microsoft Word (trademark).
[0059]
In defining the format of the web page, instructions may be given regarding the appearance of the header, toolbar, and footer portions, for example. The instructions may define templates such as these headers, toolbars, and footer portions, which may then be used in conjunction with controlling the appearance of the web page if desired.
[0060]
In performing step 602, a separate directory 714 is used to store the set of HTML templates 716 thus generated.
[0061]
In step 604, the user inserts a specified tag into the HTML template 716.
[0062]
Standard tags recognized in HTML are user defined tags for use in a given application (user defined means defined by the computer user who generated the tag) Can be augmented. In this case, the tag is intended to be used by a tool, and will be referred to as a “tool tag” hereinafter. These tool tags are ‘!! TAG It is included in the HTML that defines a predetermined template in the form of NAME !! '. TAG Two exclamation marks (exclamation points) on either side of NAME indicate the tool that, when invoked, has a predetermined relationship, typically text insertion.
[0063]
The predetermined relationship can be based on information gathered about the file structure when the tree traversal is performed. With respect to the first and second embodiments, the description of the branch form generally stored by the tool includes the name of the given directory, the relationship and name of the parent directory of the given directory, the subdirectory of the given directory. Contains information about directory relationships and names, relationships and names of other directories that share the same directory as a given directory, names of files stored in a given directory, and so on.
[0064]
A list of examples of such tool tags is shown below (Table 1).
Tool tag example (Table 1)
!! Title !! The title of the current file as text (no expansion)
To display)
!! Child Link 1 !! Link the names of all files in the directory
Show as This does not show subdirectories
The list is sorted alphabetically and each is generated
Shows the date and time when
!! Child Link 2 !! All subdirectories derived from the current directory
The list of birds is displayed as a link.
Sorted in order
!! Child Links 3 !! Overall of all text files in the current directory
The correct contents
!! Child Links 4 !! Everything that has the same parent directory as the current directory
A list that displays directory names as links is
Sorted alphabetically
!! Archive Link !! When a file is put into the archive,
A link is displayed File cannot be archived
Nothing is displayed
!! All Child 1 !! of articles added within the number of days specified by the archive
Display list
!! Parent !! A link to the directory immediately above the current directory
Generate
!! Home !! Generate a link to the homepage of the site
!! Feedback !! Any one designed to receive such feedback
A link to the email address of someone
!! Comment !! Insert text from CMT file in subdirectory
Do
!! File Text !! Displays the entire contents of the text file
!! Sibling Links 2 !! in the same subdirectory as the current text file
Display all other text files as links.
[0065]
In step 606, in this exemplary embodiment, a set of eXtensible Markup Language (XML) templates for the memory in the source file structure 700 is generated. However, it will be appreciated that other suitable forms of templates can also be used here.
[0066]
The function of these XML templates is to assemble the HTML template 716 and generate the page format as desired. Illustratively, a given XML template can call an HTML header template, an HTML title template, an HTML text template, and an HTML footer template. An example of such an HML template is as follows:
[Table 1]

[0067]
As shown in Table 1, the XML file begins with <PAGE> and ends with </ PAGE>. COMPONENT NAME is a name assigned to a part of the specified page. COMPONENT Examples of NAME are HEADER, TITLE, and FOOTER. The <FILE> tag is used to indicate the location of the HTML template in question. <TAG1> and <TAG2> are tags used in this component. As already described, such a list of tags is illustratively listed in Table 1. <TAG1> YES </ TAG1> indicates that TAG1 is used in the called template. All tags used in the template are declared this way.
[0068]
Different types of functionality are exemplarily shown by the <ARCHIVE> component:
[Table 2]

[0069]
When the <ARCHIVE> component is included, the time elapsed since the content file was stored in the respective directory is tested. The date and time of the memory of a file in a computer file system is generally obtained from the operating system as an associated characteristic of the file concerned. When applying a template containing such an archive component to a content file, if the time period is found to be longer than a predetermined time, the content file is placed in the archive. The archiving process will be further described later.
[0070]
With reference to FIG. 7, these XML templates can be stored via the source file structure 700. However, the placement of such an XML template in just one subdirectory will now be described in detail by showing the implementation of this embodiment. However, it will be appreciated that similar XML templates are seeded as desired via the source file structure 700. A third second tier subdirectory 708 is shown as storing first and second XML templates 718, 720. The function of the first XML template 718 is to define the appearance of the content file as a web page showing the assembly of the HTML template in accordance with the above. A slightly different function of the second XML template 720 is to allow the generation of the contents of directory pages that contain links to other web pages, as will be described later.
[0071]
From the point of view discussed in relation to the first and second embodiments, the first XML template 718 is said to be 'inherited' down the hierarchical source file structure 700. The effect of this 'inheritance' application will be described in more detail later.
[0072]
In step 608, a file containing global information useful for the operation of the tool can be generated. Thus, the control file 722 written in XML is stored in a separate directory 714.
[0073]
An archive file 726 is also generated and stored in a separate directory 714, for example written in XML, which functions to determine the appearance of the archive page. The global information stored in the control file 722 may be at a memory location of the archive template 726, for example.
[0074]
In step 610, the content file is introduced through the hierarchical source file structure 700. Again, by way of example, a text file (file extension, '.txt') 724 is shown as being stored in the subdirectory 708 of the third second layer. Again, it is understood that such files are stored via the source file structure 700 as desired. Again, it is well known that when using the Windows operating system, files can be stored using, for example, Windows File Manager (trademark) or Windows Explorer (trademark). .
[0075]
In step 612, a tool is called.
[0076]
The operation of the tool will now be described with further reference to FIGS.
[0077]
In general, when a tool is called, it will have at least three parameters: the location of the control file in the computer file system (in this example, a separate directory 714), the location of the source file in the computer system file (in this case the source The location of the file structure 700) and the location of the 'target' directory where the 'template processed' web page is output.
[0078]
With respect to the first and second embodiments, given the location of the source file structure 700, when invoked, the tool will first perform a so-called 'tree traversal' procedure in a top-down manner. Further, again, in the middle of the first procedure, the branch structure of the file structure relating to the root directory and the subdirectory is detected and stored by the tool. Again, as already mentioned, the branching description generally stored by the tool is the name of the given directory, the relationship and name of the parent directory of the given directory, the subdirectories of the given directory Information about the relationship and name of the directory, the relationship and name of other directories sharing the same parent directory as the given directory, and so on.
[0079]
As in the first embodiment, the tool then performs a tree traversal procedure in a bottom-up manner. This second procedure is similar to the procedure described with respect to the first embodiment, and will now be described with respect to the process flowchart shown in FIG.
[0080]
As is apparent from the above, the template used in this third embodiment is different from the template itself as described for the first and second embodiments, assembled from fragment templates. Thus, as equal to step 302, the tool searches for the first XML template 718 rather than the template of the first embodiment aspect. When this template is applied by the tool corresponding to step 304, it calls the associated HTML template 716 to assemble a specific configured template that is applied to the content file 724.
[0081]
In accordance with the method described in the inventor's pending application, an HTML file is generated using a content file 724 containing text. However, in doing this, according to the third embodiment of the present invention, an XML template assembled with an HTML template is also applied, and the new 'processed with template' file is suitable for use as a web page. Not only has the form of HTML, but also has a desired appearance according to a template, for example. In this way, the content file is converted to a 'template processed' web page.
[0082]
Assuming that the content file 724 containing the text submitted by an external author contains HTML statements, these HTML statements are honored to the extent that they do not conflict with the template HTML according to this embodiment of the invention. It should be noted that (appropriate conditions). In one example, a hyperlink may be included in the text body of the content file. With respect to the first two embodiments, the new file may of course be stored anywhere.
[0083]
Instead, however, in this third embodiment, the tool generates a 'target' file structure at the location specified for the tool at the time of the call, and the new template processed file generated by the tool is Output to this 'target' file structure. The structure of the target file directory mirrors the source file structure. Using the example source file structure shown in FIG. 7 and related to FIG. 8, a mirrored target file structure 800 is generated. The first layer root directory 802 includes first, second, and third second layer subdirectories 804, 806, and 808, and first and second third layer subdirectories 810, 812, And is shown in correspondence with FIG. The new 'template processed' file 814 corresponding to the content file 724 in the third second layer subdirectory 708 of the source file structure 700 is the third second layer sub of the target file structure 800. Stored in directory 808.
[0084]
As already described, it can be seen that templates and desired content files that take the form of both first and second XML templates 718, 720 are seeded in the source file structure 700.
[0085]
The method described above is performed for each content file stored in the source file structure 700. The related template, that is, the template corresponding to the first XML template 718 is applied to each content file, and the HTML file processed with the corresponding template is suitable for use as a web page, and has an appropriate target file structure. Output to a (sub) directory.
[0086]
The second XML template 720 and its equivalent are applied by the tool and are stored in the directory for each (sub) directory of the target file structure using the description of the source file structure 700 stored by the branched tool. Generate the document. With reference to FIG. 8, a directory document 816 is generated in the form of an HTML file suitable for use as a web page, and is illustratively shown as stored in a third, second tier subdirectory 808. Has been. Links are prepared by the HTML commands contained in this directory page 816, and for example, access to a web page that describes all 'processed by template' contents in this (sub) directory is permitted. In addition, for example, a home or root directory, a parent directory, a child (sub) directory, and a sibling directory (which shares the same parent directory), or another example, navigate an archive page.
[0087]
An 'archive' link in a directory page is directed to an archive page, for example, created and stored in the same (sub) directory as the associated directory page. In accordance with the above description of the archiving process, when an archiving tag is included in an XML template, the content file is 'archived' when it is applied to a content file stored prior to a predetermined time period. Would be considered a file. The content file is still used to generate the 'template processed' web page, but the entry does not appear in the 'current' directory page in the associated (sub) directory, rather the directory page is archived as described above. Provide a link to the web page that contains the link to the page and this link has been processed with the 'archived' template. With reference to FIG. 8, the illustrated archive page 818 is again shown as being stored in the third second tier subdirectory 808.
[0088]
As is well known, the location of the target directory in the computer file system may simply be provided in the web server application program in order to make the web page stored in the target directory available as a web site. . One example of a suitable web server application program is Microsoft Internet Information Server ™. The web server then makes the website accessible to an external web browser on the appropriate connection.
[0089]
From the above it is clear that the third embodiment of the method and tool of the present invention provides an effective means for website generation.
[0090]
As described in detail in the inventor's pending international patent application, the 'managed' website is not merely an incidental problem associated with the prior art, but simply (for example, different types Generate the appropriate form of the source file structure (related to the meeting), and the whole template structure (in this example, 'cascading down', more related to different types of meetings, more general Meeting templates are seeded and complemented or overridden to the extent provided by the identified template, and in the appropriate directory of the relevant documents (in this example, associated with each different type of meeting) Obviously it can be generated by memorizing and finally executing the method (operating tool) A.
[0091]
In addition, however, it will be appreciated that the third embodiment of the method and tool of the present invention also provides an effective means of maintaining the website by a simple means of re-executing the existing source file structure.
[0092]
When the 'look and feel' of an existing website changes, HTML templates stored in separate directories are very easily edited and executed again. The website is then regenerated using a new HTML template that defines a new 'look and feel'. In addition, the existing XML template is moved to a different directory, or a new template is directed to the appropriate directory in the source file hierarchy to change the desired path and the cascade of templates in the re-executed tool.
[0093]
New content files from various contributing authors are, of course, directed to the appropriate directories in the source file structure and re-executed tools, making the new non-new files web pages with the desired 'look and feel', Consistency with existing pages can be achieved.
[0094]
In the prior art, when web site reconfiguration is performed, it is generally required to manually modify interconnected hyperlinks. As is well known, the manual entry process often becomes a so-called 'broken link' when the document pointed to by the hyperlink no longer exists in that position.
[0095]
When restructuring is required in the third embodiment of the present invention, the tool can be used to modify the source file structure, move documents and templates closer, and perform the desired restructuring. Each time is re-executed, the generated website is newly regenerated, so that such link breakage does not occur.
[0096]
In addition, an archiving process can be performed each time the tool is run to archive older content and automatically ensure that it can still be accessed.
[0097]
As is well known, re-execution of such tools can be performed, for example, as a daily scheduled event, and can provide for sustained and effective management of the website in accordance with the present invention.
[Brief description of the drawings]
FIG. 1 is a diagram showing a general-purpose computer system.
FIG. 2 is a diagram showing a first source file structure and associated content and template files stored therein.
FIG. 3 is a flow chart of a first process for use with a first source file structure and associated content and template files stored therein.
FIG. 4 shows a second source file structure, a separate directory, and related content and template files stored therein.
FIG. 5 is a flowchart of a second process for use with a second source file structure, a separate directory, and associated content and template files stored therein.
FIG. 6 is a flowchart of a third process for setting up a third source file structure having a separate directory and storing the contents and template files associated therein.
7 shows a third source file structure set according to the process flow chart of FIG. 6 and a separate directory storing content and template files associated therewith. FIG.
FIG. 8 is a diagram showing a target file structure generated from a source file structure and related contents and a template file as shown in FIG. 7;

Claims (9)

Using a computer system that operates in accordance with an operating system, a method for generating a content file having information template processing,
The operating system can store files in a hierarchical computer file system having one or more directories, each directory can store one or more files, and can have one or more directories as subdirectories;
The method
Associating a directory with a template file suitable for controlling the appearance of the document to which the template file template is applied;
Directory includes storing a content file with information, and
According associated template file, and automatically process the content file having the information in the directory, further comprising the step of generating a content file having information corresponding template processing,
Appearance of the content file having the information template processing the corresponding is controlled by the template file associated with the method. Computer file system have been divided into the directory of the hierarchical structure,
Each directory from one directory one content file that has been stored, it is placed in hierarchical path lineal containing up to the top level directory of the directory of the hierarchical structure, each 1 or more template file directory to be associated is the one process of claim 1 wherein the associated content file with said one directory stored. The method of claim 1 or 2, wherein the step of associating a template with a directory is performed based on a template file stored in the directory. Metadata and steps to be associated with each content file,
When applying the relevant Tagged template file, any one of a respective predetermined operation against the content files, claims 1 further comprising the step of performing on the basis of metadata each associated 3 The method described. An apparatus for generating a content file having template- processed information,
A computer system that operates according to an operating system, wherein the operating system can store files in a hierarchical computer file system having one or more directories, each directory can store one or more files, and one or more directories as subdirectories Can have a computer system
When,
A means of associating a template file with a directory suitable for controlling the appearance of the document to which the template file template is applied;
Wherein according to the template file associated with the directory by the associating means, and automatically process the content file having the information in the directory, and automatic processing means for generating a content file having information corresponding template process, the ,
When it is displayed using the appropriate view application, the appearance of the content file having the information template processing the corresponding is controlled by the template file associated with the apparatus. Computer file system have been divided into the directory of the hierarchical structure,
Each directory from one directory one content file that has been stored, it is placed in hierarchical path lineal containing up to the top level directory of the directory of the hierarchical structure,
Said means to associate a template file and directory, the one or more template files that are associated with each directory, the single content file associated also with the one directory stored claims 5 Apparatus according . Wherein associating the template file and directory means, based on the template file that is stored in that directory, the association device according to claim 5 or 6, wherein performing the template and directories. Further comprising means to associate with each content file metadata,
Related Tagged in applying the template file, respective predetermined operation for each content file, device according to any one of claims 5 to 7 is executed on the basis of the relevant Tagged metadata. A readable computer program memory device by a computer, incorporating computer readable code executable by a computer, the computer program memory device to perform the method of any one of claims 1 to 4.

Images