1. 04 Oct, 2019 2 commits
  2. 03 Oct, 2019 2 commits
  3. 19 Sep, 2019 1 commit
  4. 02 Oct, 2019 14 commits
  5. 01 Oct, 2019 2 commits
  6. 02 Oct, 2019 1 commit
  7. 19 Sep, 2019 1 commit
  8. 27 Jun, 2019 1 commit
  9. 26 Jun, 2019 3 commits
  10. 02 May, 2019 3 commits
    • Denis Laxalde's avatar
      Added tag 0.17.0 for changeset 0a565615f0d5 · c339778239a5
      Denis Laxalde authored
      c339778239a5
    • Denis Laxalde's avatar
      [pkg] Version 0.17.0 · 0a565615f0d5
      Denis Laxalde authored
      0a565615f0d5
    • Denis Laxalde's avatar
      [profile gen] Account for bdo's user cardinality or its parent's in... · fcb890e6d9d7
      Denis Laxalde authored
      [profile gen] Account for bdo's user cardinality or its parent's in "Integrity" element (CONSEJIRA-663)
      
      See also https://jira.mtpl.bs.fr.atos.net/browse/CONSEJIRA-663
      
      For more details, quoting verbatim the customer request for future reference:
      
      | Sur les documents multi occurrences (0-n ou 1-n) ou même si l’archive
      | est multi occurrence (0-n ou 1-n), il y a une balise integrity qui est
      | liée au document dans le bordereau de versement que l’on génère.
      | Or, dans le XSD du profil, la balise integrity du document ne possède
      | pas l'attribut : maxOccurs="unbounded"
      | Donc lors de l'envoi à Asalae du versement, Asalae fait une vérification
      | par rapport au profil et affiche une erreur a cause de la balise
      | integrity qui est présente plusieurs fois.
      |
      | Pour moi le correctif à faire doit porter sur le XSD et le RNG sur la
      | balise integrity pour qu'elle soit multi-occurrence possible dans les cas
      | suivants :
      |
      |   *   Si le document (Document) est en multi occurrence (0-n ou 1-n)
      |       donc avec un attribut maxOccurs="unbounded"
      |   *   Si une UA (Contains) supérieure au document est en multi
      |       occurrence (0-n ou 1-n) donc avec un attribut
      |       maxOccurs="unbounded"
      
      | si une UA supérieur est en cardinalité max unbounded, alors
      | l'integrity sur les documents en dessous doit forcément être en
      | unbounded également
      
      | il faut que l'integrity soit en facultative ou multi occurrence si une
      | UA supérieure est facultative ou en multi occurrence.
      
      This is essentially achieved by looking for the upper parent archive
      units of a data object then their cardinality to produce the Integrity element.
      
      Adding tests for new integrity_cardinality() function based on customer
      examples.
      fcb890e6d9d7
  11. 23 Apr, 2019 1 commit
    • Denis Laxalde's avatar
      [test] Specify bdo's user_cardinality in test_seda_0_2_bordereau_ref · 1fe87336af7c
      Denis Laxalde authored
      In the next changeset, binary data object's user_cardinality will be
      accounted for when inserting the "Integrity" element in profile whereas
      it is currently hard-coded to "0..1" (see xsd_integrity() method of
      SEDA1XSDExport and SEDA02XSDExport classes). In order to prevent changes
      to generated profile with respect to the "seda_02_bordereau_ref.xml"
      file, we set the value of user_cardinality created bdo in this test.
      1fe87336af7c
  12. 26 Apr, 2019 1 commit
  13. 24 Apr, 2019 1 commit
  14. 08 Mar, 2019 3 commits
  15. 20 Dec, 2018 2 commits
  16. 14 Dec, 2018 2 commits
    • Denis Laxalde's avatar
      [hooks] Delete binary DO when deleting an archive unit not related to a profile · 30e67f4f9e29
      Denis Laxalde authored
      We extend the logic of "seda.doref.del" hook so that it not only handles
      the case of "simplified profile" but also the case of archive unit not
      related to a profile. In the later case, we check that the container of
      "SEDABinaryDataObject" is really a "SEDAArchiveUnit" (not sure what else
      it could be) and trigger the operation deleting the binary data-object
      when its parent object reference (SEDADataObjectReference entity) is
      deleted.
      
      Accordingly, we rename hook and operation classes and update their
      docstring.
      
      This resolves CONSEJIRA-643 but making deletion of an archive unit
      containing a binary data object but not related to profile. New test
      goes into test_schema.py below other tests related to the hook we
      modified.
      30e67f4f9e29
    • Denis Laxalde's avatar
      Refactor conditional logic in SimplifiedProfileDelRefROHook a bit · 049322b9d8ee
      Denis Laxalde authored
      This is a preparatory refactoring to ease introduction of a functional
      change in the next changeset.
      049322b9d8ee