1. 25 Jan, 2017 1 commit
  2. 20 Jan, 2017 7 commits
  3. 19 Jan, 2017 6 commits
  4. 18 Jan, 2017 1 commit
    • Sylvain Thénault's avatar
      Add dumb migration from agent to authority records · af46a867519d
      Sylvain Thénault authored
      Though this requires yet unpublished patch of cw 3.24 to not crash on addition
      of Activity (as prov is a dependancy of the eac cube).
      Test if Agent is still in the schema before dropping it, since saem_ref use the
      seda cube but also have its own definition of Agent, which we don't want to
  5. 17 Jan, 2017 1 commit
  6. 11 Jan, 2017 6 commits
    • Sylvain Thénault's avatar
      Fold content tab into archive unit's description tab · 15734eda777a
      Sylvain Thénault authored
      This requires a bit more work than expected due to monolitic implementation of
      render_attributes in cubicweb, as explained in the inline comment.
      Closes #16684017
    • Sylvain Thénault's avatar
      Eventually drop the views.content module · b37082098c56
      Sylvain Thénault authored
      Everything has been moved to the views.archiveunit module.
      Closes #16684017
    • Sylvain Thénault's avatar
      Move latest content's tab to archive unit · 21132e4f9132
      Sylvain Thénault authored
      i.e. the tab displaying content information which is not yet displayed by other
      tab (mainly controlled by uicfg rules).
      Move there pre-existing code in the same module, for the case of simplified
      Related to #16684017
    • Sylvain Thénault's avatar
      Move most content's tab to the archive unit · 999e4cf6efe9
      Sylvain Thénault authored
      The only one remaining being the default one. Along the way, rename some
      identifier and classes to be more consistent.
      The views.content module isn't modified yet, it will be dropped all at once when
      this work will be completed.
      Related to #16684017
    • Sylvain Thénault's avatar
      Remove remaining usage of dropped 'id' attributes · ff04117be4a2
      Sylvain Thénault authored
      Update rql query and use .dc_title entity method to generate label from
      annotation (prefetched).
    • Sylvain Thénault's avatar
      [profile gen] Add a special case for path through data_object_reference_id · 5f607c9702cb
      Sylvain Thénault authored
      This relation is explicitly marked as composite in shema/__init__.py to ease the
      case of simplified profiles, where we want data objects to appear as children of
      archive unit instead of references as expected by SEDA 2. Doing this, we
      introduced a bug in SEDA 2 profile generation where the target value (hence the
      referenced data object) was also considered as the 'cardinality entity' (the one
      defining the cardinality / annotation) for the associated XML element. This led
      to using the data object's cardinality / annotation for the *reference* element.
  7. 13 Jan, 2017 1 commit
  8. 11 Jan, 2017 7 commits
  9. 05 Jan, 2017 2 commits
  10. 11 Jan, 2017 3 commits
  11. 10 Jan, 2017 2 commits
    • Sylvain Thénault's avatar
      Stop using unique identifier on archive unit and data objects · 5fb5bf38f962
      Sylvain Thénault authored
      They have been introduced at a first glance to handle references during profile
      generation as well as display of 'first class' element in the UI. The main problem is
      that they clash when using the 'import archive unit' feature, since one may not
      import the same unit twice without changing the id first. Another problem is
      that their purpose is not clear to end-user.
      This changeset remove the attribute, use eid instead during profile generation
      and fix tests. UI and proper migration will be handled in later csets.
      Related #16070476
    • Sylvain Thénault's avatar
      [i18n] Fix some messages · b6a2ad4c7683
      Sylvain Thénault authored
      Closes #16688021
  12. 06 Jan, 2017 1 commit
  13. 05 Jan, 2017 1 commit
    • Sylvain Thénault's avatar
      [profile gen] Fix path_target_values wrt skipped attributes · 6a2991d3a896
      Sylvain Thénault authored
      for instance in case of restrictionEndDate, it was returning
        [(content entity, restriction end date entity)]
      instead of
        [(restriction end date entity, None)]
      This was only causing cardinality error (eg you get the content entity's
      cardinality instead of the restriction end date's one) which have been unnoticed
      until a cardinality uncompatible with attribute was used on a content node.
      Closes #16688086
  14. 11 Jan, 2017 1 commit