Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-2752

When ingesting new document types, the system errors out if parent document types are not ingested before child document types

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-1130improve performance of xml ingestion
      KULRICE-3736document type schema out of sync with UserUtils
      KULRICE-5872Apply Database Changes for Rule Action Attributes and Ingest Context Document Type
      KULRICE-2886Ingested 6 documents but response only showed that 5 had succesfully been ingested
      KULRICE-8650Kew XmlExporterTests failing on doc ingestion with length = '292' is not facet-valid with respect to maxLength '255' for type 'ShortStringType'.
      KULRICE-756Document types with orphaned nodes should result in ingestion failure
      KULRICE-4146OptimisticLockException exception when ingesting some kew files.
      KULRICE-9455Ingesting a doc type needs to flush additional caches
      KULRICE-2915When clicking on the lookup icon for "Parent Document Type" on the Document Type lookup, we need to change the label in the header of the page to read "Parent Document Type"
      KULRICE-9386Issues with doctype xml ingestion
    • Rice Module:
      KEW
    • Application Requirement:
      Rice

      Description

      If document types in a single file are ingested in this manner:

      ChildDocumentType
      ParentDocumentType

      The ingestion of "ChildDocumentType" will fail out the file during ingestion. It would be possible to check a document for a parent document type as it's being ingested. From there the child document type could be held and processed after the parent document type is processed correctly.

        • A Unit test in DocumentTypeTest or DocumentTypeXmlParserTest should be created to verify the bug first.

        Activity

        Hide
        Eric Westfall added a comment -

        Assigning to Chad. Chad I think this will be a good first task for you as it involves writing a unit test and fixing a bug on the document type XML parser.

        Show
        Eric Westfall added a comment - Assigning to Chad. Chad I think this will be a good first task for you as it involves writing a unit test and fixing a bug on the document type XML parser.
        Hide
        David Elyea added a comment -

        Chad, let me know if you run into any issues or have questions with this. Also if you just want to sit down over Skype or Jabber or something and talk through what you're seeing in the code, we can do that.

        I have a task that will force me to be within the same code but it should take me several days to get mine complete to a commitable point so you shouldn't see any synchronize conflict issues. If you do, let me know and we can resolve them together.

        Show
        David Elyea added a comment - Chad, let me know if you run into any issues or have questions with this. Also if you just want to sit down over Skype or Jabber or something and talk through what you're seeing in the code, we can do that. I have a task that will force me to be within the same code but it should take me several days to get mine complete to a commitable point so you shouldn't see any synchronize conflict issues. If you do, let me know and we can resolve them together.
        Hide
        Chad Hagstrom added a comment -

        You can disregard my second question in my previous post; I saw that the "generateNewDocumentTypeFromExisting" method evaluates a "standard" document pulled from the database. However, I still need help with one thing: how do I get/set a document type in the database so that I can unit-test the routing document processing portion?

        Show
        Chad Hagstrom added a comment - You can disregard my second question in my previous post; I saw that the "generateNewDocumentTypeFromExisting" method evaluates a "standard" document pulled from the database. However, I still need help with one thing: how do I get/set a document type in the database so that I can unit-test the routing document processing portion?
        Hide
        Eric Westfall added a comment -

        Bulk change of all Rice 1.0 issues to closed after public release.

        Show
        Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

          People

          • Assignee:
            Chad Hagstrom
            Reporter:
            David Elyea
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel