Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

  1. Steering call on Tues. Nothing to report.
  2. Can Fedora store an arbitrarily large graph?
    1. In theory it should work. Need to test it
    2. Single-subject restriction is gone
  3. Camel toolbox
    1. Get java client updated
    2. Pull out osgi related files
    3. First step getting it out of karaf and into spring and worry about configuration later
    4. The blueprints could be changed to spring java config
    5. For against Spring Boot?
      1. Boot provides a lot of integrations for free (health checks, monitoring, etc)
      2. How much stuff do we actually need? More simple without?
      3. Does it need an HTTP interface?
    6. Sprint scheduled for last week of April
  4. Migration validator is alpha
  5. No news from University of Texas - Austin
  6. Danny working on updating search index
  7. Should Fedora 3 objects always be migrated to archival groups?
    1. Archival groups do not model the on disk representation the same as Fedora 3.
    2. Archival groups do allow resources to be versioned together and for all of the resources to be grouped together on disk
      1. How much do people care about this?
    3. When a resource within an archival group is modified, it locks the entire AG to that transaction, which would not happen if the resources were not in an AG
    4. Archival groups will likely have more versions than an average resource because they are versioned every time any resource they contain is modified.

Actions