Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:08
Size: 4104
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:09:34
Size: 4114
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
The below table contains all the planned actions for this iteration. Each of the actions may contribute to the completion of one or more tasks from the [:WBS:Work Breakdown Structure] (WBS). The below table contains all the planned actions for this iteration. Each of the actions may contribute to the completion of one or more tasks from the [[WBS|Work Breakdown Structure]] (WBS).
Line 17: Line 17:
||9 || [:ActionOpenSourcing:Early open-sourcing of DOMS. ] || || None(!) ||Already described || ||
||2 || [:ActionFollowupOnOutstandingDatamodelIssues:Followup on outstanding Datamodel Issues. ] || || ["TaskA.2.2"], ["TaskA.2.3"] || Already described || Allmost Done ||
||7 || [:ActionDescribeIterationWorkFlow:Describe the iteration workflow and make a check-list. ] || || || ||Postponed ||
||1 || [:ActionSummaOnAStick:Summa on a stick (on a server)] || 2½ md || ["TaskB.2"] || TE, MKE || Done ||
||1 || [:ActionHarvestDomsToSumma:Harvest DOMS to Summa] || 2½ md || ["TaskB.2"] || TE, MKE, BAM || Done ||
||2 || [:ActionSummaIndexRepresentationDisseminators:Index Representation Disseminators]|| 7 md ||["TaskB.2"] ||JRG, ABR || Done ||
||2 || [:ActionSummaIndexAndPresentationXSLTs:XSLTs from index representation to Summa indexing/presentation] || 5 md ||["TaskB.1"] ||KFC, JRG, ABR || Done ||
||5 || [:ActionBitstorageWithIngester:Bitstorage with ingester] || 5.5 md || || ABR, TE || Done ||
||2 || [:Iteration7ReleaseTest:Release Test ] || || Release test ||JRG, TE || Done||
||9 || [[ActionOpenSourcing|Early open-sourcing of DOMS. ]] || || None(!) ||Already described || ||
||2 || [[ActionFollowupOnOutstandingDatamodelIssues|Followup on outstanding Datamodel Issues. ]] || || [[TaskA.2.2]], [[TaskA.2.3]] || Already described || Allmost Done ||
||7 || [[ActionDescribeIterationWorkFlow|Describe the iteration workflow and make a check-list. ]] || || || ||Postponed ||
||1 || [[ActionSummaOnAStick|Summa on a stick (on a server)]] || 2½ md || [[TaskB.2]] || TE, MKE || Done ||
||1 || [[ActionHarvestDomsToSumma|Harvest DOMS to Summa]] || 2½ md || [[TaskB.2]] || TE, MKE, BAM || Done ||
||2 || [[ActionSummaIndexRepresentationDisseminators|Index Representation Disseminators]]|| 7 md ||[[TaskB.2]] ||JRG, ABR || Done ||
||2 || [[ActionSummaIndexAndPresentationXSLTs|XSLTs from index representation to Summa indexing/presentation]] || 5 md ||[[TaskB.1]] ||KFC, JRG, ABR || Done ||
||5 || [[ActionBitstorageWithIngester|Bitstorage with ingester]] || 5.5 md || || ABR, TE || Done ||
||2 || [[Iteration7ReleaseTest|Release Test ]] || || Release test ||JRG, TE || Done||

Summa integration and bit storage

Begun
Finished
Status
Finished
Due
2008-01-31
Title
Summa integration and bit storage

In this iteration we will address summa integration and bit storage. At the end of the iteration, we should have the summa service interface ready, and ingest capable of storing files. Essentially this will leave us with a working system.

Iteration Actions

The below table contains all the planned actions for this iteration. Each of the actions may contribute to the completion of one or more tasks from the Work Breakdown Structure (WBS).

Each action is associated with a priority, estimated time, tasks addressed, responsible developers and a status. The priority indicates the importance of the completion of the action, where the highest priority is indicated with 1, and the status indicates the current state of the action. The state may be one of the following: "Not Started", "In Progress" and "Completed".

Priority

Action Description

Estimated time

Tasks adressed

Responsible

Status

9

Early open-sourcing of DOMS.

None(!)

Already described

2

Followup on outstanding Datamodel Issues.

TaskA.2.2, TaskA.2.3

Already described

Allmost Done

7

Describe the iteration workflow and make a check-list.

Postponed

1

Summa on a stick (on a server)

2½ md

TaskB.2

TE, MKE

Done

1

Harvest DOMS to Summa

2½ md

TaskB.2

TE, MKE, BAM

Done

2

Index Representation Disseminators

7 md

TaskB.2

JRG, ABR

Done

2

XSLTs from index representation to Summa indexing/presentation

5 md

TaskB.1

KFC, JRG, ABR

Done

5

Bitstorage with ingester

5.5 md

ABR, TE

Done

2

Release Test

Release test

JRG, TE

Done

Time used

From 18/12-07 to 26/2-08

  • Disseminator: ABR=7 md
  • XSLT: ABR=1md
  • Bitstorage: ABR=3.5 md
  • Summa: ABR=4md
  • Releasetest: ABR=9md

Total: ABR=24.5 md.

Total workdays in period (not counting fridays): 32

AOB

Gentofte Availability

We have learned that the Gentofte collection should not be made freely available. Organisations need to subscribe (ie. pay) for access, but there didn't exist a login system. Rather, the access was filtered based on ip and such. But as you paid a fixed amount, no matter the use, the system was required to provide a log (of IPs) that access Gentofte Material, in order to detect abuse.

In order to make the Gentofte Collection available again, we need to replicate this behaviour. As the search results themselves are not protected, we need to log the opening of files themselves.

But as this is Gentofte specific, dumping in on Drift might not be an option, depending on the systems behind the bitstorage. So I guess we will have to pipe the files through SUMMA, rather than let users access the files in bitstorage, and then make SUMMA log the access.

We need to discuss the implications of this. Discussed: This problem will fall to Hans, who will find an agreement with Drift. We are thinking about wrapping the storage server for the gentofte collection in a proxy, that filters the IPs. The DOMS team will deliver the list of IPs, but we hope that the maitenance of ther server can be done by Drift. Drift has agreed to this.

Iteration07 (last edited 2010-03-17 13:09:34 by localhost)