Page tree

Versions Compared

Key

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

...

  1. Islandora / F4 migration update
  2. Open Repositories committer meeting planning
  3. From last week: High-priority issues

    Expand
    • Audit issues:
      • internal/external URIs
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1507
    • LDP
      1. post/patch constrained-by 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1418
      2. put to fail if triples not persisted 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1417
      3. disallow put/patch with RDF that includes other subjects 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1411
    • Performance
      1. GC error 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1294
      2. blank node map 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1302
    • Clean up
      1. remove UUID from default transform 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1552
      2. remove UUID from responses 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1539
      3. remove Blanknode from ontology 
        Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1394
  4. 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

  5. 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

  6. ...

...

  • Some migration-utils issues turned out to be difficult
    • Utility will maintain a list of mappings during migration
    • Currently no tooling to address URL redirects at the application level (e.g. redirecting a legacy F3 URL request to the new F4 URL)
      • Aaron plans on using a key-value store to handle the redirects
        • Use a service to do a lookup in the database and redirect to the new F4 URL
  • Pull request to provide properties file to declare namespace prefixes before migration starts
    • Otherwise default namespaces get created (ns01, ns02, etc.)
    • Namespace prefixes can’t be changed once created (as per ModeShape). But they can be remapped
    • Could build a separate utility to make such changes. Would not be accessible via API
    • Andrew will create a ticket 
      Jira
      serverDuraSpace JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-1567

OR2015 conference planning 

  • PCDM - making sure our efforts are aligned
    • What aspects of PCDM are now implemented in Sufia? Do we all agree and plan to implement elsewhere accordingly?
    • Perhaps discuss over lunch?
    • Google Doc signup sheet? Doodle poll?
  • Committers meeting
    • People should come with a plan to be actively involved in the discussions
    • Agenda online
    • Software dependencies
      • Packages, OSGi support, dependency chains, etc. 
    • Migrations plans
      • When are people migrating?
      • What are the blockers?