Browse Prior Art Database

Single Click To Un-Federate/Reverse Federate Of Mixed Documents To Multiple Source Repositories Using Custom Metadata

IP.com Disclosure Number: IPCOM000232387D
Publication Date: 2013-Nov-05
Document File: 4 page(s) / 57K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a cross-federation process with a Single-Click Reverse-Federation User Interface (UI) feature that solves issues related to the incorrect entering of data or criteria, federating and unfederating documents and metadata, the accidental deletion of documents, etc. The solution is a method for using a single-click Reverse Federation UI that allows the user to perform searches for federated documents, un-file or delete, and then export these documents to a special set of reverse-federation tables in a reverse-federation database. The solution also includes a reverse importer to import back these documents to the original folders and update version date/check-in date.

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

Page 01 of 4

Single Click To Un-Federate/Reverse Federate Of Mixed Documents To Multiple Source Repositories Using Custom Metadata

Many issues exist related to the unfederation or reverse federation of documents. Following are examples of issues that must be addressed:


• Documents with metadata that are federated from multi-source repositories to a target repository with incorrect data mapping can result in errors and bad rows in the federation database. These documents might then be deleted from the source repositories by a user.


• If a user federates the wrong sets of documents and metadata and then files documents to the target folder in the target repository, it is difficult to later un-file and un-federate the document(s) perform a database cleanup, and restore/reverse-federate documents back to the source repository's folder with the original metadata/properties and re-federate using different sets of documents.


• A user might specify the wrong range and wrong criteria of documents from

multiple source repositories. If the user then federates these documents from multi-source repositories to a central repository, the result is only a partial federation and/or documents being filed to the wrong folder on the target repository. The user then wants to perform clean up on the target repository and federation data to un-federate and reverse-federate these documents back to the correct source repository (and re-federate). This scenario is applicable to both the existing source folder and the new source folder.


• A user might accidentally delete source repository documents while the

federation process is still in progress, which results in errors in both the

federation tables and the delete requests propagated to the target repository. This then leads to errors and improper cleanup or deletion of documents on the target repository and database tables. The user wants to clean up the database tables, remove errors, un-file/un-federate documents on the target repository, reverse-federate/restore documents with metadata back to the source repository, and delete federated documents on the target repository.


• A user wants to federate to a target repository, reverse federate documents back to a different source repository, and federate from that new source repository to a new target repository.

A user is forced to go through an error prone and manually intensive process to correct these scenarios.

The disclosed cross-federation process with a Single-Click Reverse-Federation User Interface (UI) feature addresses the above issues. The discl...