대표
청구항
▼
1. A method for managing a change to a collection of records, the method including: maintaining the collection of records and a pending change to the collection of records in a data storage system, wherein at least some of the records each include a metadata map that maps one or more source values to one or more target values, and the pending change having been previously proposed and validated but not yet applied to the collection of records; andvalidating a proposed change to the collection of records specified by an input received over a user interfac...
1. A method for managing a change to a collection of records, the method including: maintaining the collection of records and a pending change to the collection of records in a data storage system, wherein at least some of the records each include a metadata map that maps one or more source values to one or more target values, and the pending change having been previously proposed and validated but not yet applied to the collection of records; andvalidating a proposed change to the collection of records specified by an input received over a user interface, the validating including: querying the data storage system based on one or more validation criteria associated with the proposed change;receiving a first result in response to the querying indicating any records in the collection of records that include information that would be affected by the proposed change;processing the pending change, the pending change being different from the proposed change;determining a second result based on the processing indicating whether or not there are any conflicting records in the pending change that represent a potential conflict with the proposed change;generating a third result based on the first result and the second result indicating any records in the collection of records or in the conflicting records that include information that would be affected by the proposed change; andprocessing the third result to determine whether the proposed change is valid according to the one or more validation criteria. 2. The method of claim 1, wherein processing the third result includes invalidating the proposed change if the same set of one or more source values is mapped by two or more different metadata maps to two or more different sets of one or more target values, or two or more different sets of one or more source values are mapped by two or more different metadata maps to the same set of one or more target values. 3. The method of claim 1, wherein processing the third result includes identifying whether applying the proposed change would result in a creation of one or more duplicate records. 4. The method of claim 3, wherein identifying whether applying the proposed change would result in a creation of one or more duplicate records includes identifying one or more duplicate rows. 5. The method of claim 3, wherein the one or more duplicate rows are identified using one or more source values as the one or more validation criteria. 6. The method of claim 1, wherein the pending change includes one or more changesets that represent proposed changes to the collection of records that have been entered into the user interface. 7. The method of claim 1, wherein the input includes an instruction to apply changes associated with a previously-saved changeset to the collection of records. 8. The method of claim 1, wherein validating the proposed change to the collection of records includes validating the proposed change against other proposed changes specified in the user interface by the input. 9. The method of claim 1, wherein the user interface includes one or more filters to selectively display one or more subsets of sets of records. 10. The method of claim 1, further including generating a notification if the proposed change is not validated. 11. The method of claim 10, wherein the notification identifies a portion of the proposed change that violates the one or more validation criteria. 12. The method of claim 1, wherein the pending change is stored in the data storage system prior to receiving the input specifying the proposed change to the collection of records. 13. The method of claim 1, wherein querying the data storage system includes identifying one or more portions of the metadata map that are relevant to the proposed change. 14. The method of claim 13, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 15. The method of claim 1, wherein the pending change includes a metadata map that maps one or more source values to one or more target values, and processing the pending change includes identifying one or more portions of the metadata map that are relevant to the proposed change. 16. The method of claim 15, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 17. The method of claim 1, wherein the proposed change includes a metadata map that maps one or more source values to one or more target values. 18. A non-transitory computer-readable storage medium storing a computer program for managing a change to a collection of records, the computer program including instructions for causing a computing system to: maintain the collection of records and a pending change to the collection of records in a data storage system, wherein at least some of the records each include a metadata map that maps one or more source values to one or more target values, and the pending change having been previously proposed and validated but not yet applied to the collection of records; andvalidate a proposed change to the collection of records specified by an input received over a user interface, the validating including: querying the data storage system based on one or more validation criteria associated with the proposed change;receiving a first result in response to the querying indicating any records in the collection of records that include information that would be affected by the proposed change;processing the pending change, the pending change being different from the proposed change;determining a second result based on the processing indicating whether or not there are any conflicting records in the pending change that represent a potential conflict with the proposed change;generating a third result based on the first result and the second result indicating any records in the collection of records or in the conflicting records that include information that would be affected by the proposed change; andprocessing the third result to determine whether the proposed change is valid according to the one or more validation criteria. 19. The non-transitory computer-readable storage medium of claim 18, wherein processing the third result includes invalidating the proposed change if the same set of one or more source values is mapped by two or more different metadata maps to two or more different sets of one or more target values, or two or more different sets of one or more source values are mapped by two or more different metadata maps to the same set of one or more target values. 20. The non-transitory computer-readable storage medium of claim 18, wherein processing the third result includes identifying whether applying the proposed change would result in a creation of one or more duplicate records. 21. The non-transitory computer-readable storage medium of claim 20, wherein identifying whether applying the proposed change would result in a creation of one or more duplicate records includes identifying one or more duplicate TOWS. 22. The non-transitory computer-readable storage medium of claim 20, wherein the one or more duplicate rows are identified using one or more source values as the one or more validation criteria. 23. The non-transitory computer-readable storage medium of claim 18, wherein the pending change includes one or more changesets that represent proposed changes to the collection of records that have been entered into the user interface. 24. The non-transitory computer-readable storage medium of claim 18, wherein the input includes an instruction to apply changes associated with a previously-saved changeset to the collection of records. 25. The non-transitory computer-readable storage medium of claim 18, wherein validating the proposed change to the collection of records includes validating the proposed change against other proposed changes specified in the user interface by the input. 26. The non-transitory computer-readable storage medium of claim 18, wherein the user interface includes one or more filters to selectively display one or more subsets of sets of records. 27. The non-transitory computer-readable storage medium of claim 18, the computer program further including instructions for causing the computer system to generate a notification if the proposed change is not validated. 28. The non-transitory computer-readable storage medium of claim 27, wherein the notification identifies a portion of the proposed change that violates the one or more validation criteria. 29. The non-transitory computer-readable storage medium of claim 18, wherein the pending change is stored in the data storage system prior to receiving the input specifying the proposed change to the collection of records. 30. The non-transitory computer-readable storage medium of claim 18, wherein querying the data storage system includes identifying one or more portions of the metadata map that are relevant to the proposed change. 31. The non-transitory computer-readable storage medium of claim 30, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 32. The non-transitory computer-readable storage medium of claim 18, wherein the pending change includes a metadata map that maps one or more source values to one or more target values, and processing the pending change includes identifying one or more portions of the metadata map that are relevant to the proposed change. 33. The non-transitory computer-readable storage medium of claim 32, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 34. The non-transitory computer-readable storage medium of claim 18, wherein the proposed change includes a metadata map that maps one or more source values to one or more target values. 35. A computing system for managing a change to a collection of records, the computing system including: a data storage system comprising one or more data storage devices for maintaining the collection of records and a pending change to the collection of records, wherein at least some of the records each include a metadata map that maps one or more source values to one or more target values, and the pending change having been previously proposed and validated but not yet applied to the collection of records; andat least one hardware processor configured to validate a proposed change to the collection of records specified by an input received over a user interface, the validating including: querying the data storage system based on one or more validation criteria associated with the proposed change;receiving a first result in response to the querying indicating any records in the collection of records that include information that would be affected by the proposed change;processing the pending change, the pending change being different from the proposed change;determining a second result based on the processing indicating whether or not there are any conflicting records in the pending change that represent a potential conflict with the proposed change;generating a third result based on the first result and the second result indicating any records in the collection of records or in the conflicting records that include information that would be affected by the proposed change; andprocessing the third result to determine whether the proposed change is valid according to the one or more validation criteria. 36. The computing system of claim 35, wherein processing the third result includes invalidating the proposed change if the same set of one or more source values is mapped by two or more different metadata maps to two or more different sets of one or more target values, or two or more different sets of one or more source values are mapped by two or more different metadata maps to the same set of one or more target values. 37. The computing system of claim 35, wherein processing the third result includes identifying whether applying the proposed change would result in a creation of one or more duplicate records. 38. The computing system of claim 37, wherein identifying whether applying the proposed change would result in a creation of one or more duplicate records includes identifying one or more duplicate rows. 39. The computing system of claim 37, wherein the one or more duplicate rows are identified using one or more source values as the one or more validation criteria. 40. The computing system of claim 35, wherein the pending change includes one or more changesets that represent proposed changes to the collection of records that have been entered into the user interface. 41. The computing system of claim 35, wherein the input includes an instruction to apply changes associated with a previously-saved changeset to the collection of records. 42. The computing system of claim 35, wherein validating the proposed change to the collection of records includes validating the proposed change against other proposed changes specified in the user interface by the input. 43. The computing system of claim 35, wherein the user interface includes one or more filters to selectively display one or more subsets of sets of records. 44. The computing system of claim 35, wherein the processing unit is further configured to generate a notification if the proposed change is not validated. 45. The computing system of claim 44, wherein the notification identifies a portion of the proposed change that violates the one or more validation criteria. 46. The computing system of claim 35, wherein the pending change is stored in the data storage system prior to receiving the input specifying the proposed change to the collection of records. 47. The computing system of claim 35, wherein querying the data storage system includes identifying one or more portions of the metadata map that are relevant to the proposed change. 48. The computing system of claim 47, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 49. The computing system of claim 35, wherein the pending change includes a metadata map that maps one or more source values to one or more target values, and processing the pending change includes identifying one or more portions of the metadata map that are relevant to the proposed change. 50. The computing system of claim 49, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 51. The computing system of claim 35, wherein the proposed change includes a metadata map that maps one or more source values to one or more target values. 52. A computing system for managing a change to a collection of records, the computing system including: means for maintaining the collection of records and a pending change to the collection of records in a data storage system, wherein at least some of the records each include a metadata map that maps one or more source values to one or more target values, and the pending change having been previously proposed and validated but not yet applied to the collection of records; andmeans for validating a proposed change to the collection of records specified by an input received over a user interface, the validating including: querying the data storage system based on one or more validation criteria associated with the proposed change;receiving a first result in response to the querying indicating any records in the collection of records that include information that would be affected by the proposed change;processing the pending change, the pending change being different from the proposed change;determining a second result based on the processing indicating whether or not there are any conflicting records in the pending change that represent a potential conflict with the proposed change;generating a third result based on the first result and the second result indicating any records in the collection of records or in the conflicting records that include information that would be affected by the proposed change; andprocessing the third result to determine whether the proposed change is valid according to the one or more validation criteria. 53. The computing system of claim 52, wherein processing the third result includes invalidating the proposed change if the same set of one or more source values is mapped by two or more different metadata maps to two or more different sets of one or more target values, or two or more different sets of one or more source values are mapped by two or more different metadata maps to the same set of one or more target values. 54. The computing system of claim 52, wherein processing the third result includes identifying whether applying the proposed change would result in a creation of one or more duplicate records. 55. The computing system of claim 54, wherein identifying whether applying the proposed change would result in a creation of one or more duplicate records includes identifying one or more duplicate rows. 56. The computing system of claim 54, wherein the one or more duplicate rows are identified using one or more source values as the one or more validation criteria. 57. The computing system of claim 52, wherein the pending change includes one or more changesets that represent proposed changes to the collection of records that have been entered into the user interface. 58. The computing system of claim 52, wherein the input includes an instruction to apply changes associated with a previously-saved changeset to the collection of records. 59. The computing system of claim 52, wherein validating the proposed change to the collection of records includes validating the proposed change against other proposed changes specified in the user interface by the input. 60. The computing system of claim 52, wherein the user interface includes one or more filters to selectively display one or more subsets of sets of records. 61. The computing system of claim 52, further including means for generating a notification if the proposed change is not validated. 62. The computing system of claim 61, wherein the notification identifies a portion of the proposed change that violates the one or more validation criteria. 63. The computing system of claim 52, wherein the pending change is stored in the data storage system prior to receiving the input specifying the proposed change to the collection of records. 64. The computing system of claim 52, wherein querying the data storage system includes identifying one or more portions of the metadata map that are relevant to the proposed change. 65. The computing system of claim 64, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 66. The computing system of claim 52, wherein the pending change includes a metadata map that maps one or more source values to one or more target values, and processing the pending change includes identifying one or more portions of the metadata map that are relevant to the proposed change. 67. The computing system of claim 66, wherein a portion of the metadata map is relevant to the proposed change when a source value or a target value in the portion of the metadata map matches a source value or a target value identified in the proposed change. 68. The computing system of claim 52, wherein the proposed change includes a metadata map that maps one or more source values to one or more target values.
