CN1643517A - Life-cycle management engine - Google Patents
Life-cycle management engine Download PDFInfo
- Publication number
- CN1643517A CN1643517A CNA03806281XA CN03806281A CN1643517A CN 1643517 A CN1643517 A CN 1643517A CN A03806281X A CNA03806281X A CN A03806281XA CN 03806281 A CN03806281 A CN 03806281A CN 1643517 A CN1643517 A CN 1643517A
- Authority
- CN
- China
- Prior art keywords
- record
- file plan
- life cycle
- file
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A records manager manages life cycle phases of records managed by a host application program. The records manager is in communication with the host application program over a network and includes a file plan database, a record management engine, and an applications program interface. The file plan database includes at least one file plan object, with each file plan object having a life cycle rule. The record management engine includes filing means and determining means. The filing means files record identifiers within the file plan objects in accordance with record profile data received over the network. The determining means tracks changes in the life cycle phases for the records from the life cycle rules. The applications program interface is in communication with the record management engine, and is configured to transmit to the host application program over the network indications of the changes in the life cycle phases.
Description
Technical field
The present invention relates to a kind of system that is used for managing electronic record.Specifically, the present invention relates to a kind of maintenance of managing electronic record and engine of processing of being used for.
Background technology
The existing recorded management system comprises database, its each all be associated with separately electronical record.Usually, each comprises and indicates title, author, open date, theme, the state of relative recording and the field of position.In addition, each also may comprise record and keep data field, and this field indicates the time period that this record should be archived to storage thereafter, and the time period that should destroy the record that is filed thereafter.
Usually, record management system has been used to manage paper storehouse or other tangible documents.Yet, consider popularizing of electronic document, such as word processing document, electronic form document, drawing document and Email, people have attempted to be provided for the software solution of managing electronic record, comprise that it keeps and processing.
For example, in 1993, Mutoh (US 5379423) has described a kind of computer based information life cycle management system, comprising: the memory device of the information that information management program, user can be associated with information object from its terminal, the data processing storage space that is used to store the information object with specific life cycle state and storage of sending the request of processing.The signal of being stored comprises: the former generation/offspring's information object classification of the owner of each information object, the user who allow to use each information object, each information object and the life cycle data of each information object (such as life cycle state, between state condition or the opportunity and the life cycle state sequence of transforming object).Disclosed life cycle state comprises: approved state (content of object goes through, but does not also allow to use the situation of this contents of object), open state (allowing to use the situation of contents of object), seal state (forbidding that anyone uses the situation of contents of object except that the owner) and revocation status (wherein object is deleted) up for safekeeping.
When receiving the request of processing (such as request) from terminal for the definition object, information management program presents list object to the user, this list object permission user specifies the information of the object that will generate, such as information object level, life cycle information, user and access rights thereof.Next, if information management program is received request of access or state transform request, then under institute's requested operation condition consistent with the owner/user profile and life cycle information, information management program carries out this operation.If information management program is in response to the state transform request of coming self terminal, information object is carried out state transformation, then information management program also carries out any necessary life cycle conversion to the determined offspring's information object of former generation/offspring's level or former generation's information object by this object, and with in the storage space that each information object moves to its new life cycle status is associated.If information object has been transformed revocation status, then information management program is also deleted this information object.
In nineteen ninety-five, Johnson (US 5813009) discloses a kind of computer based information location management system, and this system comprises: data filter is used for handling the electronical record of arrival; One or more permanent storage appliances (for example WORM base plate) are used for stored record; Database, it comprises the information that is associated with record; And records manager interface.This patentee has described a kind of classification filing structure (hierarchical filing structure) of record, this structure comprises: " file cabinet " of expression physical storage locations, " the files type " of expression file type (for example contract), " file " of the particular instance of expression former generation files type, and " document " of representing single document in " file ".
Data filter is configured to receive electronical record, comprises image, word processing file and speech data of being scanned or the like.When receiving electronical record, data filter checking record header comprises suitable filing and index data (for example physical storage locations, data/time, maintenance data).Then, the data filter additional database is used for following the tracks of the label of memory location, and the maintenance data that are associated with this record.Then, by this record of storage in one of " forever " memory device and with keeping data and this data to file position renewal database in structure at this, perhaps automatically or the intervention by the operator, the record that " evaluation " received.For deletion record from permanent storage after helping, storage has the record of similar maintenance period on identical physical storage device.
Records manager can regularly use the interface to come Query Database, to obtain having the tabulation prior to all records on destruction date of Query Dates.Then, records manager can change the maintenance data of any one list records, and from permanent storage all or any list records of deletion.If any being recorded in outside the described storer stored, then the storer of records manager outside described storer given an order, (a plurality of) electronical record that the request deletion is specified.When receiving the affirmation of having deleted specified electronical record, records manager is new database more, to reflect this deletion.
Though Mutoh and Johnson disclose the total solution that writes down to the managing electronic of deleting from initially, must from the environment of creating record, record copies be come out.The high-level efficiency data processing that provides record is provided Mutoh is requisite measure, and Johnson discloses that to allow individual knowledge and the technical ability of this record of judge's mechanism evaluation storage be requisite measure, thereby decides whether accept the record stored.As a result, Mutoh and Johnson must realize access protocal and corresponding user interfaces, to prevent the unauthorized access for institute's stored record.Generally have access protocal of himself and the user interface of himself because be used for creating the software environment of record, so these solutions have unnecessarily increased required computational resource.
In addition, though Johnson record is disclosed can be by automated validation, to be used by information management program, automated validation need write down arrival and carry the suitable filing and the data filter of index data.Because Johnson discloses record with the storage of classification filing structure, so the user must be familiar with the operation of this information management program, so that desired filing data to be provided at least.This requirement has hindered the popularization of this information management program, especially learns the user of multiple user interfaces for being unwilling.
Therefore, people experience following needs for a long time: a kind of gratifying management system of managing electronic record.
Summary of the invention
According to a first aspect of the invention, a kind of method of managing electronic record is provided, comprise following steps: (1) by network receive with by the related uniquely record identifier of the record of application program management, record management engine is configured to manage the life cycle state of this record, and this record identifier comprises the profile data of relative recording; (2) according to relevant profile data, file the record identifier that is received in the file plan node of file plan, each described file plan node all has relevant maintenance rule; (3) according to described maintenance rule, for life cycle state determined in the record of being managed; And (4) send life cycle instructions by described network, to ask described application program separately life cycle state transferred in the record of being managed.
A kind of computer-readable medium that has carried the processing instruction of computing machine also is provided, and when this processing instruction was loaded into this computing machine, it made this computing machine carry out the above-mentioned steps sequence.
According to the present invention second aspect is arranged, a kind of computer based is provided, has promoted the electronical record of the record by application program management being carried out life cycle management to manage engine.This record management engine comprises: receiving-member, file parts, determine parts and parts are provided.Receiving-member is configured to receive the record identifier that is associated with record by described application program management, and wherein this record identifier comprises the profile data of relative recording.The filing parts are configured to file the record identifier that is received according to relevant profile data in the file plan node of file plan, and wherein each described file plan node all has relevant life cycle rule.Determine that parts are configured to according to described life cycle rule, for life cycle state determined in the record of being managed.Provide parts to be configured to send life cycle instructions, separately life cycle state transferred in the record of being managed to ask described application program by described network.
A kind of computer-readable medium that has carried the processing instruction of computing machine also is provided, and when this processing instruction was loaded into this computing machine, it defined above-mentioned receiving-member, files parts, determines parts and parts are provided.
According to the present invention the third aspect is arranged, a kind of record management server that is used for managing by the life cycle of the record of application program management is provided.This record management server and host application program are by network service, and include file planning database, record management engine and application programming interfaces.Described file plan database comprises at least one file plan node, and wherein each described file plan node all has life cycle rule.Record management engine comprises filing parts and definite parts.The filing parts are filed record identifier according to the record profile data that receives by network in the file plan node of file plan.Determine that parts are configured to according to described life cycle rule, the life cycle phase of track record changes.Application programming interfaces are communicated by letter with record management engine, and are configured to send to host application program by network the variation indication of life cycle phase.
According to a forth aspect of the invention, provide a kind of computer based, promotion the record by application program management to be carried out the electronical record management engine of life cycle management.This record management engine and host application program be by network service, and comprise: database interface, the limiting-members really of communicating by letter with database interface, and with the application programming interfaces of filing parts and definite components communicate.Database interface is used for the access file planning database, described file plan database comprises at least one file plan node, and each described file plan node all comprises: the life cycle that the life cycle phase of the object that management is associated with this document plan node changes keeps rule.The filing parts are filed record identifier according to the respective profiles of record in the corresponding document plan node, wherein said profile receives by network.Determine that parts change according to the life cycle phase of life cycle rule track record.Application programming interfaces are configured to send to described host application program by described network the variation indication of life cycle phase.
A kind of computer-readable medium that has carried the processing instruction of computing machine also is provided, and when this processing instruction was loaded into this computing machine, it defined above-mentioned database interface, files parts, determines parts and application programming interfaces.
According to a fifth aspect of the invention, provide a kind of computer based, be used for to the management engine of management by the life cycle of the record of application program management.This management engine be configured to host application program by network service, and comprise: be used for the interface of access file planning database, and with filing parts and definite parts of this interface communication.This interface is used for: the access file planning database, described file plan database comprises at least one file plan node, and each described file plan node all comprises: the life cycle that the life cycle phase of the object that management is associated with this document plan node changes keeps rule.The filing parts are according to filing record identifier from each respective record profiles that application program receives by network the corresponding document plan node.Determine that parts are recorded in different life transition between the stage according to corresponding life cycle rule with what manage.
A kind of computer-readable medium that has carried the processing instruction of computing machine also is provided, and when this processing instruction was loaded into this computing machine, it defined above-mentioned database interface, files parts, determines parts and application programming interfaces.
According to a sixth aspect of the invention, provide a kind of computer based, promotion the record by application program management to be carried out the electronical record management engine of life cycle management.This record management engine and host application program are by network service, and comprise: database interface, the definition component of communicating by letter with database interface, the filing parts of communicating by letter with database interface, the limiting-members really of communicating by letter with database interface, and with the application programming interfaces of definition component, filing parts and definite components communicate.Database interface is used for the access file planning database, described file plan database comprises at least one file plan node, and each described file plan node all comprises: the life cycle that the life cycle phase of the object that management is associated with this document plan node changes keeps rule.The definition component definition comprises the file plan of at least one file plan node, comprises: parent child node, file plan object class, at least one file plan attribute and life cycle keep rule.The filing parts are filed record identifier according to the respective profiles of record in the corresponding document plan node, wherein said profile receives by network.Determine that parts change according to the life cycle phase of life cycle rule track record.Application programming interfaces are configured to send to described host application program by described network the variation indication of life cycle phase.
A kind of computer-readable medium that has carried the processing instruction of computing machine also is provided, and when this processing instruction was loaded into this computing machine, it defined above-mentioned database interface, files parts, determines parts and application programming interfaces.
Description of drawings
Now with reference to as an example accompanying drawing only the present invention is described, wherein:
Fig. 1 is the synoptic diagram of record management system, has shown terminal, host computer server and record management server;
Fig. 2 is the figure of the structure of display file planning database;
Fig. 3 is the synoptic diagram of record management server shown in Figure 1;
Fig. 4 is the process flow diagram of displayed record management system operation.
Embodiment
Forward Fig. 1 now to, it has shown a kind of electronical record management system, it summarizes expression by 100, comprises: at least one terminal 102, host computer server 104, be used for managing the record management server 200 and the communication network 108 of the life cycle of the record of being managed by host computer server 104.Preferably, communication network 108 comprises promotion between terminal 102 and host computer server 104, between terminal 102 and record management server 200 and the network of communicating by letter between host computer server 104 and record management server 200.Yet replacedly, the function of terminal 102 and record management server 200 can realize on the common computer server, promotes the communication network 108 of communicating by letter between terminal 102 and the computer server as long as this common computer server has.In addition, communication network 108 can omit fully, and the function of terminal 102, host server 104 and record management server 200 can realize on single computing machine.
Usually, host application program 114 maintenance customer accounts (comprising user's name and password) database, and the group definition that is provided to the controlled access of computer recording to the terminal user.Record management server 200 is used user and the group account information of being safeguarded by host application program 114, is provided to the controlled access (by host application program 114) of record management server 200 with the user to terminal 102.Yet, in a kind of variant, host application program 114 is maintain individual user or group account not, and host application program 114 is by " guest " account access record management server 200, in this case, record management server 200 can not per user ground be implemented the restriction to record management server 200.
Preferably, record management server 200 uses COM or Simple Object Access Protocol (SOAP) assembly to communicate by letter with host application program 114.Correspondingly, preferably, host application program 114 comprises interface 116, and this interface can or meet the object interaction of SOAP with com object.In addition, preferably, record management server 200 is the server based on WINDOWS 2000, and host application program 114 should be able to operate under WINDOWS 2000 server environments in this case.
Accession (registration):
When the life cycle by the record of host server 104 management has exhausted and this record should be sent to external authorization mechanism when forever filing, record management server 200 is called this function.In response, host application program 114 with this record copies to record management server transfer directory specified in funcall.In order to ensure not conflict in transmitting catalogue, host application program 114 usefulness title HostId.HostRecordId.ext with recording storage in transmitting catalogue, wherein HostId is the peculiar host identification of host application program 114, HostRecordId is the peculiar sign of this project in host server 104, ext is the local extension name (doc for example of host record, elm, xml or the like).
After host record was copied in the transmission catalogue, host application program 114 should write down deletion from host server 104.Then, host application program 114 provides following XML data structure to record management server 200, this XML data structure indicates the fullpath that transmits this record in the catalogue, and the profile data items in the host server 112 that host application program 114 is original with this record is associated.
Delete (deletion):
Destroy (destruction):
When the life cycle by the record of host server 104 management has exhausted and should be with this record from host server 112 during eternal the deletion, record management server 200 is called this function.In response, preferably, host application program 114 should write down deletion from host server 104, yet host application program 114 can be selected not do like this.Then, host application program 114 provides following XML data structure to record management server 200, this XML data structure indicates the fullpath of this record in the host server 112, and host application program 114 originally with host server 112 that this record is associated in profile data items.
GoupList (Groups List):
UserList (user list):
TransitionToPhase (transferring to the stage):
UnRegister (unregistered):
When user's deleted file plan objects 122 and when indicating life cycle that host application program 114 should no longer consider relevant record by record management server 200 management, record management server 200 is called this function from file plan.
With reference to Fig. 2, file plan database 110 is embodied as SQL database, and comprises the record of the file plan of definition record management system 100.File plan is to be used for being categorized as the node hierarchy layout of the layout of any desirable standard of reflection by the electronical record that host application program 114 is managed.The keeper just can create or realize file plan by indicating parent child node 120, file plan object class and file plan attribute 124, life cycle code 126 and suspension status 128 for each file plan node 120.For example, node can be arranged in the classification based on theme (for example theme, author, title), even in the location-based classification (for example storehouse, corridor, file cabinet), with the physical location of reflection respective physical record.
File plan has four steps in the defined file planning database 110.These steps are: (1) defined file planning " view ", how mutual (2) constitute the assembly or the file plan 122 of this document planning, the relation between (3) these assemblies, and the relevant assembly of (4) management rule.
File plan view is described the mode of organizational information.It is the set of the relation between the assembly of configuration file planning.For example, the planning of AUS logo file comprises four types assembly---record series, record sort, file and record, and each has all defined the info class that narrows down in succession.Existence begins to the single classification clue of file end from record series.Same information can think that interchangeable mode or view organize.For example, can come organizational information according to the physical location of record---building, floor, corridor, cubbyhole and file.More than recording storage in two examples in hierarchial file structure planning, promptly file plan component or file plan 122 are interrelated with offspring-former generation's relation.Described engine is supported a plurality of classifications and non-graded view, and for the file plan component that comprises wherein, these views may be overlapping or discrete.
File plan component definitions in file plan the canned data class.Each file plan comprises at least one assembly.For the file plan founder the assembly that can define number without limits.The component definition of configuration file planning info class.Each assembly in the file plan all has different titles, attribute and behavior.The user can indicate the file plan component of configuration file planning.File plan component definitions has the attribute that a cover is determined the file plan component behavior.These attributes comprise title and front view.Name is called file plan component and other the dissimilar unique identifiers that make a distinction with particular type.The example of file plan component definition names comprises: record series, record type, file and record.Front view is that any file plan component all must exist file plan view wherein.
Dissimilar file plan component has the set of different file plan attribute 124, and it is used to provide other information of relevant file plan component.For example,, then in planning, may have the not file of restricted number, but All Files folder is all with the common set of shared file plan attribute 124 if file plan comprises the file plan 122 that becomes " file ".The value that is stored in each file can be different, but attribute self will be present in the All Files folder of file plan.The attribute of file plan component " file " can press from both sides peculiar identifier, position or the like by include file.Conversely, each file plan attribute definition has the community set of its behavior of management.For example, attribute must be specific data type (integer, real number, date, currency or the like).The user also can limit size of data or the data volume that is stored in the given attribute definition.
The pass that may be present between the dissimilar file plan component is following statement: two file plan component are can ad hoc fashion interrelated.Contextual definition comprises three kinds of attributes: this concerns the file plan component type or the file plan 122 of an end (source), this concerns the file plan component type or the file plan 122 of the other end (target), and should the affiliated file plan view of relation.For example, if file plan is classification, then the relation between the file plan component can be characterized as being former generation-offspring.
The structure of file plan database 110 shows in Fig. 2.As shown in the figure, file plan database 110 comprises a plurality of file plan record 118, and each all is associated with file plan node, and has indicated the former generation's node 120a and the child node 120b of this document plan node.In addition, each file plan record 118 is include file plan object field 122 all, and attribute field 124, life cycle code field 126, delay (suspension) mode field 128, and the processing mandate field 130 of each file plan object field 122.
File plan object field 122 can be characterized by node corresponding 120 " file " object, " file " object or " record " object.Consistent with the graded properties of file plan, file object can the include file object, folder object and record object.Folder object can comprise a plurality of related record objects.For example, the record object that is stored in the folder object may be relevant by theme and/or author.The record object is preserved and the related uniquely identifier of being managed by host application program 114 of host record.Correspondingly, the record object can have the related uniquely identifier with any electronic data that can be managed by host application program 114 of word processing record, electrical form record, desktop publishing record, multimedia file, executable computer program, database or other.
Attribute field 124 indicates one or more profile data items of each object, such as " author ", " theme " and " item code ".Preferably, when the attribute 124 of keeper's defined file of record management server 200 planning, the value of the also pre-defined attribute 124 of this keeper, and definition " pick-list (pick list) ", when the user registered (following discussion) host record in record management system 100, this pick-list allowed the user to select from the value of predefined attribute 124.The keeper can be associated pick-list by limiting " customized profile " (following will discussion) with one or more users.Thus, for example, if file plan attribute 124 has indicated department's item code, then the keeper can fill pick-list with all effective item codes, then node 120 suitable in this pick-list and the file plan is associated.When the user attempts when file plan is inserted new host record, record management server 200 will present effective item code with alternative to the user.
Life cycle code field 126 is indispensable fields, and it indicates the life cycle phase of associated file plan object 122.In order to make record management server 200 can realize life cycle management, the various life cycle phases of keeper's identification document plan objects 122 of record management server 200 (for example block (cutoff), registration or destroy), and the sequence that will pass through of each record of registering with record management server 200.Then, the keeper distributes life cycle code (LCC) 126 for each life cycle phase, and definition keeps rule, the parameter that this maintenance rule definition management document plan objects 122 shifts between life cycle phase.When the user in record management server 200 during registration, the user must insert one of defined life cycle code 126 in life cycle code field 126.
Life cycle code field 126 comprises name sub-field, disposition type sub-field and phase sub-field.Name sub-field comprises the identifier of unique identification life cycle code 126.Disposition type field indicates when associated file plan object 122 arrival keep the period to finish, the activity that host application program 114 is carried out.For example, disposition type field can indicate when keeping the period to finish and the exterior storage storehouse is destroyed or be sent to file plan 122.
The time period that phase sub-field specified document plan objects 122 is spent in each life cycle state, and the level of security that object is received when object enters each life cycle state (following description).Phase sub-field is the cutoff information of include file plan objects 122 also.Usually, when file plan 122 enters cutoff phase, be limited for the visit of file plan 122.For example, if file plan 122 is a file object, then when file plan 122 remained on cutoff phase, record management server 200 can be configured to prevent that the user from adding object to file plan 122.
Cutoff information comprises: whether indication file plan 122 enters the cutoff flag of cutoff phase, sign cutoff phase Start Date block cycle date, and indicate the cut frequency that in a year, applies the frequency of blocking.If plan objects 122 enters cutoff phase, then block the period up to next, just begin the maintenance period of this object, prolonged the maintenance period of this object reality thus.
For example, if the cycle date of blocking of file plan 122 is January 1, and cut frequency is every half a year, then blocks being judged to be annual January 1 and July 1.If in record management server 200, register plan objects 122, and distributed the maintenance rule that defines the cutoff phase sequence, then block being judged to be 1 year active maintenance stage, and dormancy in 2 years has kept the stage in Dec 1 (its life cycle date); If the current life cycle phase of appointment is a cutoff phase in life cycle code 126, any file plan 122 that then has this life cycle code 126 all will be in cutoff phase, until January 1.After this, the host record that is associated with file plan 122 will have 3 year life-span (not being 3 years from date on Dec 14) of finishing the date of cutoff phase from file plan 122, after this host record will or by deletion from host server (handling type) or be transferred to and be the specified processing authorized location 130 (if life cycle code 126 has the registration process type) of file plan 122 if life cycle code 126 has deletion.
As shown in Figure 2, except file plan record 118, file plan database 110 also comprises security table 132, global access table 134, object access table 136 and file plan view table 138, and may comprise custom profile table 140.The user that record management server 200 tables 132 restriction safe in utilization is identified is for the visit of record management server 200, and the control user function that is authorized to carry out when login record management server 200.
Security table 132 comprises the certificate data of host server 104, and the authentication and the function authorization data of local and host accounts.Host server authentication data comprises HostID file, Host/Alias file and Alias/DSN file.The HostID file comprises the item that indicates hostid, Hostname and host password respectively.Hostid is record management server 200 numerals that distribute, unique identification host server 104.Hostname is unique descriptive name of host server 104, the place that its indication file plan record 118 rises.Host password is an encrypted entry, and host server 104 must provide this to record management server 200, to visit this record server as the host subscriber.
The Host/Alias file is to comprise the XML file of representing Hostname and host alias item respectively.Record management server 200 is used the Host/Alias file, so that Hostname is mapped to Alias.The Alias/DSN file is to comprise to represent that respectively Hostname, database connect the XML file of word string and database password item.Database connects the required ADO information of correct file plan database 110 that word string comprises record management server 200 processing host servers 104.Database password is the encrypted entry that is used for handling file plan database 110.
Local user generally is preserved for the administrator, and can be by directly visiting from one of terminal 102 login record management server 200.Because the local user is up to signing in to server just for known to the record management server 200, thus the certificate data of each local user security table record comprise user ID item and corresponding password entry both, to verify each local user's identity.On the other hand, host accounts is preserved for non-administrative users, and can only be by host application program 114 visits.Because the host subscriber has signed in to host server 104,, and do not comprise password entry so the certificate data of each local user security table record only comprises the user ID item.
Except the authentication and function authorization data of this locality and host accounts, security table 132 also comprises the record that comprises local group and both authentications of host groups and function authorization data.Record management server 200 use group authentications and function authorization data, with identification user's classification, and to such other all member's assigns authorized functions.
The keeper of record management server 200 must create local group by explicitly.On the contrary, when host user requests arrives the visit of record management server 200, host application program 114 provides host identification, host password, signs in to the user's of host server 104 user ID to record management server 200, and the tabulation of all groups under the host subscriber.Record management server 200 compares corresponding item in host identification, host password and the HostID file, is authorized to sign in to record management server 200 with checking host server 104.Then, record management server 200 is determined the host alias of host server 104 according to the Host/Alias file, and according to Host/DSN file specified data storehouse connection word string, uses relevant database password to sign in to file plan database 110 then.When host application program 114 successfully during log file planning database 110, record management server 200 is stores group list in security table 132, and signs in to specified member's update group tabulation of file plan database 110 with each host subscriber.
Global access table 134 comprises the record that comprises the visit data of all object types of realizing in file plan.Record management server 200 is used global access table 134 data, allows each user and/or organizes the operation of carrying out at each file plan object class (for example file, file, record) with overall situation control.Each access list 134 records all are linked to the record of security table 132, and for each user and/group specifies this user or group to allow the file plan object operations of carrying out.General file plan object operations comprises interpolation, deletion and changes permission.
Object access table 136 comprises the record that comprises the visit data of each file plan.Record management server 200 is used object access table 136 data, with the operation that control allows each user and/or group to carry out at each file plan 122, surmounts the overall situation permission that is provided with thus in global access table 134.Each object access table 136 record all is linked to corresponding file plan record 118, and is that each file plan 122 specifies each user of permission or group to operate.Consistent with the graded properties of file plan, be applied to all offsprings that permission on the file plan 122 also is applied to file plan 122.
The subclass of file plan view table 138 files listed plan objects 122, and the relation between the file plan 122 of identification document plan objects subclass.Specified relation can be classification, two-way or unidirectional.In hierarchical view, if the property value of file plan 122 is not also specified, then file plan 122 is from former generation's object of this document plan objects 122 (perhaps former generation's object of former generation's object, if the property value of former generation's object is not specified yet) inherited attribute value.Hereditable attribute comprises life cycle code 126, suspension status 128, handles mandate 130 and security table.
Two-way and unidirectional view defined respectively in the view folk prescription between the All Files plan objects 122 to and the twocouese relation.In two-way or unidirectional view inherited attribute not.The two kinds of view types in back have defined the relation of the non-graded between the object in the file plan, such as " cross reference " relation or " classification " relation.
Custom profile table 140 has defined attribute 124 subclass at least one file plan 122, and has listed the user who allows to check attribute set.In addition, custom profile table 140 has indicated for each attribute 124 whether this attribute 124 is read-only, and whether this attribute 124 is indispensable, and identification distribution is given the default value of this attribute 124 or selected table.Record management server 200 is used custom profile table 140 to control and is allowed the mode of user's input for the data of any file plan.For example, if file plan include file plan objects 122, this object has attribute " project status ", only allow this object of manager's visit, then the keeper of record management server 200 can define " general " profile of eliminating " project status " attribute, and " manager " profile that comprises " project status " attribute.As a result, no matter when view file plan 122, all will show suitable attribute 124 according to its supervisor status separately.
Network manager's object 210 is the program based on explorer, its administrator to terminal 102 is provided to the simplification interface of API 212, and the enterprise that allows the administrator to develop and manage for the record of being managed by host server 104 thus keeps strategy.Preferably, network manager's object 210 usefulness IIS 5.0 and Active Server Page (ASP) 3.0 are realized.
API 212 is provided to the visit of record management engine 214 to terminal 102, and uses XML to transfer data to client application (realizing) on terminal 102 or send data from client application.Preferably, API 212 usefulness are positioned at the com object realization that COM+ uses, and provide com interface to network manager's object 210 and host application program 114, COM or Simple Object Access Protocol (SOAP) interface 116 for example by in host application program 114, realizing, thus allow host application program 114 not to be carried out Visitor Logs supervisor engine 2 14 under the big situation about reconfiguring requiring.
Record management engine 214 management are shifted by the life cycle of the record of host application program 114 management.Record management engine 214 is communicated by letter with file plan database 110, and is exposed to (expose) host application program 114 by API 212, is exposed to terminal 102 by the combination of network manager's object 210 and API 212.Preferably, record management engine 214 encapsulates all SQL DBMS visits by com interface, and is embodied as the COM+ application of supporting ORACLE and SQL SERVER.This COM+ uses and is configured to carry out following manager function (using network manager's object 210):
The file plan design:
The rule of the tissue of the record of being managed by host server 104 is managed in definition
File plan realizes:
Definition is used to insert the file plan 112 of file plan, comprises the safety rule of appointed object
Life cycle management:
The maintenance rule of the maintenance of definition management document plan objects 112
Life cycle is handled:
Report:
Generate the report of object in the relevant document planning
Safety:
Definition user and group access, and user and the mandate of group function
Except being configured to carry out the above function, this COM+ uses the object that also comprises definition record identifier receiver 216, object 218, the object 220 that defines the parts of determining life cycle state and the definition of defined file planning filing parts provides the object 222 of the parts of life cycle instructions.Replacedly, the object that comprises the COM+ application can be realized on independent server, so that load balance to be provided.In addition, use, should be appreciated that it also can realize in dedicated electronic hardware, even be embodied as the combination of hardware and software though described the COM+ that is embodied as software application.
Record identifier receiver 216 is configured to receive the record identifier that is associated with the record of being managed by host application program 114 from host application program 114.Record identifier wishes for the purpose of life cycle tracking that with the user who signs in to host application program 114 record of registration is associated in record management server 200.Record identifier comprises: host application program 114 is used for the profile metadata (for example " author ", " theme " and " item code ") of categorical attribute of the identifier field of unique identification record and identification record.
As mentioned above, when the attribute 124 of keeper's defined file of record management server 200 planning, the pick-list (or menu) of the predetermined value of all right defined file plan attribute 124 of keeper is so that the user can easily provide above-mentioned profile metadata to record management server 200.Therefore, in one embodiment of the invention, record identifier receiver 216 is configured to seek the customized profile 140 that is associated with the user, and is provided at any default attribute value and any pick-list that defines in the customized profile 140 to the user.The user selects property value from pick-list (or menu), import the suitable field of any other property value to customized profile 140, sends it back desired profile metadata to record identifier receiver 216 then.
Replacedly, in another embodiment of the present invention, host application program 114 provides the copy of the profile data that host application program 114 is associated with record in the host server 112 to record identifier receiver 216, and 216 configurations of record identifier receiver are analyzed the profile data that received in the hope of required profile metadata.Therefore, when the user who signs in to host application program 114 wished record sort to the suitable file plan node 120 of record management system 100, record identifier receiver 216 was not having automatically to extract required profile metadata under the situation of manual intervention.
File plan filing parts 218 are configured to file the record identifier that receives from host application program 114 in the suitable node 120 of file plan.In order to accomplish this point, file plan is filed profile metadata and the file plan object definitions that parts 218 relatively comprise with record identifier, and according to the profile metadata record identifier is inserted in suitable file plan node 120.
Life cycle determines that parts 220 are configured to determine the life cycle state of the selected record of registration in record management server 200.In order to accomplish this point, the keeper moves inquiry on file plan record 118, can move to the next stage of its life cycle or the tabulation of manageable file plan 122 with request.For each file plan 122 of the specified inquiry of coupling, life cycle determines that parts 220 keep rule to its life cycle code 126 estimations separately, to find its corresponding maintenance expired file plan 122 of period.
Life cycle instructions provides parts 222 to be configured to provide this application program of request the record of being found to be transferred to the instruction of next life cycle state to host application program 114.In order to accomplish this point, life cycle instructions provides parts 222 to upgrade corresponding file cycle codes for expired file plan 122, thus file plan 122 is transferred to its next life cycle state.Life cycle instructions provides parts 222 also to give an order to host application program 114, transfers to its new life cycle phase separately with the record that requesting host application program 114 will be associated with residue file plan 122.
Describe the life cycle management process that realizes by record management system 100 in detail now with reference to Fig. 4.Originally, the keeper of record management system 100 uses a terminal 102 with by providing user ID and password to sign in to record management engine 214 to network manager's object 210.If user ID and password match user ID in security table 132 and corresponding password, then API 212 allows keeper's service recorder supervisor engine 2 14.
In case the keeper is login record supervisor engine 2 14 successfully, in step 500, the keeper is by following definition procedure file plan: for each file plan node 120 indicates parent child node 120, file plan object class and file plan attribute 124, life cycle code 126 and suspension status 128.The keeper also fills security table 132 with following data: local user's certificate data of the administrator of (a plurality of) host identities verification msg of host application program 114, be authorized to check/editing files planning, be authorized to Visitor Logs supervisor engine 2 14 the host subscriber host subscriber's certificate data and identify each user/group and be authorized to function authorization data with the function of record management server 200 execution.In addition, the keeper also fills global access table 134 and object access table 136 with the visit data that identifies the operation that is allowed for file plan 122, use the view that allows for file plan to fill file plan view table 138, and create desirable any custom profile table 140.Record management engine 214 is maintained in the file plan database 110 file plan thus defined.
After having defined file plan, in step 502, the user who signs in to host application program 114 states the life cycle that record management server 200 should the management host record.Usually, the user will create and/or edit host record, and will state that record management should create or the life cycle of edit phase management host record when finishing.The user can automatically state host record, such as by the host record on the Shutdown Hosts server 104, perhaps states host record by hand, such as suitable frame on the electronic profile list that passes through to select to be generated by host application program 114.
When the record announce step was finished, in step 504, the record that host application program 114 registrations are stated was in order to carrying out life cycle management by record management server 200.In order to accomplish this point, at first host application program 114 provides host identification and password to API 212, and if the item in the parameter matching HostID file that is received, then API 212 is provided to the visit of record management engine 214 to host application program 114.Host application program 114 also provides the user's who signs in to host server 104 user ID to API 212, and the tabulation of all groups under this host subscriber.These parameter access Host/Alias file and Alias/DSN file that record management engine 214 is used afterwards in the hope of database password, use database password to sign in to suitable file plan database 110 then.
In step 506, by providing the profile metadata to record management engine 214, host application program 114 with the record sort stated to cover in the suitable node 120 of file plan.The user can be automatically or the record stated of classification manually.
A kind of method before using (record sort automatically), host application program 114 provides host application program 114 with its profile data that is associated with the record of being stated (for example to recorder device 216, title, author, open date and theme), and recorder device 216 is analyzed the profile data that is received, in the hope of required profile metadata.Recorder device 216 is also with user ID inquiry custom profile table 140, to seek any default attribute value, to be included in the profile metadata.This method is useful, because it allows the life cycle phase of record management engine 214 administrative institute's statement record under the situation that does not need to understand independent user interface or new software program.
Use back a kind of method (manual classification approach), the user ID inquiry custom profile table 140 that recorder device 216 usefulness are received seeking user's customized profile, and presents all properties field 124 that customized profile allows the user to check to the user.Recorder device 216 also is provided at any default attribute value and any pick-list that defines in the customized profile to the user.The user selects property value from pick-list, and any other property value of input sends object information to record management engine 214, then as required profile metadata in suitable field.Though be not so good as automatic classification method like that to user friendly, but manual classification approach is useful still the time, because it allows record management engine 214 not needing the host subscriber to understand the life cycle phase of the record of administrative institute's statement under the situation of new software program.
After with the record sort of being stated, in step 508, record management engine 214 uses the profile metadata to provide for the appropriate location of profile metadata in file plan.In order to accomplish this point, file plan filing parts 218 compare profile metadata and the file plan object definitions that is received, and create suitable file plan 122 in file plan database 110.Then, file plan filing parts 218 distribute the profile metadata to give new file plan 122, and distribute life cycle date to give file plan 122.Life cycle date is generally file plan 122 and is added to date in the file plan database 110, yet the administrator can indicate the replacement date of life cycle date subsequently.
In step 510, file plan filing parts 218 distribute and the corresponding to life cycle code in the position of file plan 122 in the file plan classification (LCC) 126 to file plan 122, and upgrade security table 132 is authorized to execution on file plan 122 with reflection function.As follows, Any user can be limited by the level of security that is applied on the host application program 144 in the function of carrying out on the file plan 122.
File plan filing parts 218 also notify host application program 144 present being recorded in the record management engine 214 of stating to register.Preferably, the entitlement of host application program 144 assignment record is given group of administrators, and is read-only with all non-administrator group memberships' user to the access authority limitation of this record.Because record management server 200 is not preserved the copy by the record of host application program 144 management, so record management server 200 is not duplicated safety and the access function that has been realized by host application program 144, do not need to be used for the independent storage space of host record yet.In addition, because being independent of host application program 144 ground, realize file plan filing parts 218, so by utilizing the computational resource that is generally used by host application program 144, the process of the file plan 122 in the archive file planning is not disturbed host application program 144.
After having registered host record in record management engine 214, the administrator can management host be recorded in that it is appointed, keep the transfer of period between the life cycle state of final processing from initial registration by each.In order to accomplish this point, the administrator signs in on the record management engine 214 by providing user ID and password to network manager's object 210.If user ID and password match are included in user ID and corresponding password in the security table 132, then API 212 allows keeper's service recorder supervisor engine 2 14.
After the keeper successfully signed in to record management engine 214, in step 512, keeper's query note supervisor engine 2 14 was in the hope of the next stage that can move to its life cycle or the tabulation of manageable file plan 122.General query argument comprises file plan (a plurality of) branch that will check, and be used for life cycle calculations with reference to the date.The keeper can also indicate the state of cutoff flag, and next life cycle phase of wishing to be used for file plan 122.
According to Query Result, life cycle determines that parts 220 eliminatings do not have the life cycle date or the file plan 122 of its corresponding life cycle date after the reference date of being distributed and do not consider.In addition, for each remaining file plan 122, life cycle is determined the further inspection of those file plan 122 that parts 220 eliminatings are delayed, and determines life cycle code 126 that it is relevant then.
If a file plan 122 does not have the life cycle code 126 of being distributed, then life cycle determines that parts 220 recursively check former generation's object of object, finds life cycle code 126 up to it.Then, in step 514, life cycle determines that 126 estimations of 220 pairs of life cycle code of parts keep rule, keep expired file plan 122 of period to find it.
After having been found that expired file plan 122, life cycle instructions provides parts 222 to provide its corresponding tabulation that keeps expired file plan 122 of period to the keeper.From this tabulation, any object that the keeper removes or delays not wish to handle.Then, in step 516, record management engine 214 is upgraded the life cycle code separately 126 of residue file plan 122, thus file plan 122 is transferred to its next life cycle phase.In step 518, life cycle instructions provides parts 222 also to give an order to host application program 114, transfers to its new life cycle phase separately with the record that requesting host application program 114 will be associated with residue file plan 122.
If for any file plan 122 new life cycle phases is " deletion ", then life cycle instructions provides parts 222 to remove the file plan 122 that will destroy from file plan database 110, and give an order to host application program 114, delete the record that is associated with specified file plan 122 with requesting host application program 114.Should be noted that does not need the specific record of host application program 114 deletion, and just requires it to upgrade host server 122 to indicate the no longer life cycle phase of the record that indicates of administrative institute of record management server 200.
Similarly, if for any file plan 122 new life cycle phases is " registration ", then life cycle instructions provides parts 222 to remove the file plan 122 that will register from file plan database 110, and give an order to host application program 114, the record that will be associated with specified file plan 122 with requesting host application program 114 moves in the specified transmission catalogue.After the transmission catalogue has transmitted host record, record management engine 214 can be sent to host record to be the specified processing authorized location 130 of corresponding document plan objects 122 from transmitting catalogue, perhaps signal, represent that it should be sent to record by handling the storage site that authorized location 130 is managed from sending catalogue to handling authorized location 130.
Claims (21)
1. the method for managing electronic record comprises following steps:
By network receive with by the related uniquely record identifier of the record of application program management, record management engine is configured to manage the life cycle state of this record, this record identifier comprises the profile data of relative recording;
According to relevant profile data, in the file plan node of file plan, file the record identifier that is received, each described file plan node all has relevant maintenance rule;
According to described maintenance rule, for life cycle state determined in the record of being managed; And
Send life cycle instructions by described network, separately life cycle state transferred in the record of being managed to ask described application program.
2. according to the method for claim 1, also comprise following steps:
File plan in the defined file planning database, at least one file plan node is specified in this document planning; And
The wherein said maintenance rule that is associated with each file plan node keeps rule for life cycle.
3. according to the method for claim 1 or 2, the record profile of wherein said each record of being managed of application maintenance, and described record identifier receiving step comprises following steps: the record profile that receives relative recording from described application program, and analyze this record profile, in the hope of relevant profile data.
4. according to the method for claim 1 or 2, wherein said record identifier receiving step comprises following steps: the menu of file plan node is provided, and according to the menu of node menu is selected to determine the associated profiles data.
5. according to the method for claim 1 or 2, wherein said file plan node comprises: the life cycle code of the life cycle state of sign relative recording, and identify the suspension status sign whether this relative recording should shift between the stage in different life, and described life cycle state determining step comprises: at life cycle code, keep rule with reference to the state estimation of date and described Status Flag.
6. according to the method for claim 1 or 2, wherein said file plan comprises: the hierarchical arrangement of file plan node, at least one file plan node does not comprise life cycle code, and described life cycle state determining step comprises: at the life cycle code that is associated with former generation's node of described at least one file plan node, for described at least one file plan node estimation keeps rule.
7. according to the method for claim 1 or 2, wherein said file plan comprises: the non-graded of file plan node is arranged, at least one file plan node does not comprise life cycle code, and described life cycle state determining step comprises: at the life cycle code that is associated with former generation's node of described at least one file plan node, for described at least one file plan node estimation keeps rule.
8. the record management engine of a promotion to carrying out life cycle management by the record of application program management, this record management engine comprises:
Receiving-member is used for receiving the record identifier that is associated with record by described application program management by network, and this record identifier comprises the profile data of relative recording;
The filing parts are used for filing the record identifier that is received according to relevant profile data in the file plan node of file plan, and each described file plan node all has relevant life cycle rule;
Determine parts, be used for according to described life cycle rule, for life cycle state determined in the record of being managed; And
Parts are provided, are used for sending life cycle instructions, separately life cycle state transferred in the record of being managed to ask described application program by described network.
9. record management engine according to Claim 8 also comprises:
Database interface, be used for the access file planning database, described file plan database comprises at least one file plan node, and each described file plan node all comprises: the life cycle that the life cycle phase of the object that management is associated with this document plan node changes keeps rule;
Application programming interfaces, itself and described filing components communicate, and described definite parts are configured to send to described host application program by described network the variation indication of life cycle phase; And
Wherein said filing parts are communicated by letter with described database interface with definite parts.
10. record management engine according to Claim 8 also comprises:
The file plan definition component, be used for file plan in the defined file planning database, described file plan comprises: at least one file plan node, each described file plan node comprise that the life cycle that the life cycle phase of the object that management is associated with this document plan node changes keeps rule.
11. according to Claim 8 to 10 each record management engine, the record profile of wherein said each record of being managed of application maintenance, and described receiving-member is configured to receive from described application program the record profile of relative recording, and analyze this record profile, in the hope of relevant profile data.
12. to 10 each record management engine, wherein said receiving-member is configured to provide the menu of file plan node according to Claim 8, and according to the menu of node menu is selected to determine the associated profiles data.
13. according to Claim 8 to 10 each record management engine, wherein said file plan node comprises: the life cycle code of the life cycle state of sign relative recording, and identify the suspension status sign whether this relative recording should shift between the stage in different life, and described definite parts are configured at life cycle code, keep rule with reference to the state estimation of date and described Status Flag.
14. record management engine according to claim 13, wherein said file plan comprises: the hierarchical arrangement of file plan node, at least one file plan node does not comprise life cycle code, and described definite parts are configured to the life cycle code that is associated at former generation's node of described at least one file plan node, are that described at least one file plan node estimation keeps rule.
15. record management engine according to claim 13, wherein said file plan comprises: the non-graded of file plan node is arranged, at least one file plan node does not comprise life cycle code, and described definite parts are configured to the life cycle code that is associated at former generation's node of described at least one file plan node, are that described at least one file plan node estimation keeps rule.
16. a record management server that is used for managing by the life cycle of the record of application program management, this record management server and host application program comprise by network service:
File plan database comprises at least one file plan, and each described file plan all has life cycle rule;
According to Claim 8 to 15 each record management engine, and
Application programming interfaces, it is communicated by letter with file plan database, and described application programming interfaces are configured to send to described application program by network the variation indication of life cycle phase.
17. according to the record management server of claim 16, wherein said file plan database comprises the record type field of the related object that is used for each file plan, and the attribute field that defines described profile data.
18. according to the record management server of claim 16, wherein said file plan database comprises the file plan view table that concerns between the file plan of at least one defined file plan objects subclass and this document plan objects subclass.
19. according to the record management server of claim 16, wherein said file plan database comprises at least one sign for the attribute set of at least one file plan and at least one user's the custom profile table that allows to check the described application program of this attribute set.
20. according to the record management server of claim 16, wherein said file plan database comprises definition at least a accessing operation of at least one file plan and at least one user's the Access Control List (ACL) that allows to carry out the described application program of this accessing operation.
21. one kind comprises the computer program that is used for carrying out according to the computer code of each step in the claim 1 to 7.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US36812602P | 2002-03-29 | 2002-03-29 | |
| US60/368,126 | 2002-03-29 | ||
| US10/158,849 | 2002-06-03 | ||
| US10/158,849 US7233959B2 (en) | 2002-06-03 | 2002-06-03 | Life-cycle management engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1643517A true CN1643517A (en) | 2005-07-20 |
Family
ID=28677923
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA03806281XA Pending CN1643517A (en) | 2002-03-29 | 2003-03-28 | Life-cycle management engine |
Country Status (6)
| Country | Link |
|---|---|
| EP (1) | EP1490794A2 (en) |
| JP (1) | JP4166704B2 (en) |
| CN (1) | CN1643517A (en) |
| AU (1) | AU2003217044A1 (en) |
| CA (1) | CA2483457C (en) |
| WO (1) | WO2003083719A2 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104391745A (en) * | 2014-10-13 | 2015-03-04 | 浪潮通用软件有限公司 | Extensible object life cycle management method |
| CN107079284A (en) * | 2014-09-15 | 2017-08-18 | 欧贝特科技公司 | For the method for the life cycle for managing communication configuration file |
| CN113366397A (en) * | 2019-02-04 | 2021-09-07 | 西门子股份公司 | Method for searching for consistent records of pipelines in planning system, planning system and control program |
| CN115687333A (en) * | 2022-09-27 | 2023-02-03 | 西部科学城智能网联汽车创新中心(重庆)有限公司 | V2x big data life cycle management method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0290342A (en) * | 1988-09-28 | 1990-03-29 | Hitachi Ltd | Information life cycle processor |
| US5379423A (en) * | 1988-09-28 | 1995-01-03 | Hitachi, Ltd. | Information life cycle processor and information organizing method using it |
| JP2001344106A (en) * | 2000-05-31 | 2001-12-14 | Nec Corp | Dynamic access right control system for object |
-
2003
- 2003-03-28 WO PCT/GB2003/001385 patent/WO2003083719A2/en active Application Filing
- 2003-03-28 EP EP03712432A patent/EP1490794A2/en not_active Withdrawn
- 2003-03-28 AU AU2003217044A patent/AU2003217044A1/en not_active Abandoned
- 2003-03-28 CN CNA03806281XA patent/CN1643517A/en active Pending
- 2003-03-28 CA CA002483457A patent/CA2483457C/en not_active Expired - Lifetime
- 2003-03-28 JP JP2003581071A patent/JP4166704B2/en not_active Expired - Fee Related
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107079284A (en) * | 2014-09-15 | 2017-08-18 | 欧贝特科技公司 | For the method for the life cycle for managing communication configuration file |
| CN107079284B (en) * | 2014-09-15 | 2020-06-05 | 欧贝特科技公司 | Method for managing life cycle of configuration file, user identity module and terminal |
| CN104391745A (en) * | 2014-10-13 | 2015-03-04 | 浪潮通用软件有限公司 | Extensible object life cycle management method |
| CN113366397A (en) * | 2019-02-04 | 2021-09-07 | 西门子股份公司 | Method for searching for consistent records of pipelines in planning system, planning system and control program |
| CN115687333A (en) * | 2022-09-27 | 2023-02-03 | 西部科学城智能网联汽车创新中心(重庆)有限公司 | V2x big data life cycle management method and device |
| CN115687333B (en) * | 2022-09-27 | 2024-03-12 | 西部科学城智能网联汽车创新中心(重庆)有限公司 | V2x big data life cycle management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2003083719A3 (en) | 2004-01-22 |
| JP2005527895A (en) | 2005-09-15 |
| EP1490794A2 (en) | 2004-12-29 |
| CA2483457A1 (en) | 2003-10-09 |
| JP4166704B2 (en) | 2008-10-15 |
| CA2483457C (en) | 2007-11-13 |
| AU2003217044A1 (en) | 2003-10-13 |
| WO2003083719A2 (en) | 2003-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7233959B2 (en) | Life-cycle management engine | |
| US9298417B1 (en) | Systems and methods for facilitating management of data | |
| US7836080B2 (en) | Using an access control list rule to generate an access control list for a document included in a file plan | |
| US8752045B2 (en) | Methods and apparatus for using tags to control and manage assets | |
| CN110192198B (en) | Security for accessing stored resources | |
| US8719691B2 (en) | Document providing system and computer-readable storage medium | |
| US7792757B2 (en) | Systems and methods for risk based information management | |
| JP2008547118A (en) | Granting unified authority for heterogeneous applications | |
| US8204949B1 (en) | Email enabled project management applications | |
| US20070112784A1 (en) | Systems and Methods for Simplified Information Archival | |
| JP5852340B2 (en) | Dynamic management of role membership | |
| US11216581B1 (en) | Secure document sharing in a database system | |
| CA2667264A1 (en) | Systems and methods for information organization | |
| WO2014036199A2 (en) | Method for generating social network activity streams | |
| US11669630B1 (en) | Background service to generate data dictionary metadata | |
| JP2004094958A (en) | Data management system, database access method, and security mechanism | |
| US11775559B1 (en) | Distributing large amounts of global metadata using object files | |
| CN1643517A (en) | Life-cycle management engine | |
| Singh et al. | Evaluation of approaches for designing secure data warehouse | |
| JP2007304831A (en) | Approval management system | |
| US12050710B2 (en) | Generating data dictionary metadata | |
| US20240111784A1 (en) | Distributing large amounts of global metadata using object files | |
| EP4345643A1 (en) | Distributing large amounts of global metadata using object files | |
| US11989164B2 (en) | Data dictionary metadata for marketplace listings | |
| EP4345639A1 (en) | Background service to generate data dictionary metadata |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20050720 |