|
Size: 1812
Comment:
|
Size: 2715
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| Methods needed in Summa integration component, as an implementation of the Summa storage API: | === First thoughts on choice of integration with Summa === |
| Line 9: | Line 9: |
| We need an implementation of Summa's ReadableStorage interface, that is, the following methods | There are three ways in which Summa can receive content for indexing (and presentation) * By the DOMS side calling an ssh-script to deliver a zip file of contents to Summa * By the Summa side requesting latest changed objects via OAI-PMH * By the DOMS side implementing the Summa API, through which Summa can request latest changes The last option appears to be the most convenient for our use. Reason: The first would require more development on our part than the last. And the second is less convenient for Summa than the last. So, the last it is. === Overview of the work needed for Summa integration === The following is an overview of what work needs to be done by the different groups. === Methods needed in Summa integration component, as an implementation of the Summa storage API === We need an implementation of Summa's !ReadableStorage interface, that is, the following methods |
| Line 12: | Line 31: |
| * getRecord(String id, QueryOptions options) * getRecords(List of Strings id, QueryOptions options) * getRecordsModifiedAfter(long time, String base, QueryOptions options) |
* getRecord(String id, !QueryOptions options) * getRecords(List of Strings id, !QueryOptions options) * getRecordsModifiedAfter(long time, String base, !QueryOptions options) |
| Line 18: | Line 37: |
| See Summa Storage API javadoc at ... | See Summa Storage API javadoc at (where?) |
| Line 22: | Line 41: |
| {{attachment:SummaIntegrationIndexing.png}} {{attachment:SummaIntegrationDisplay.png}} |
Analysis of Task 31
First thoughts on choice of integration with Summa
There are three ways in which Summa can receive content for indexing (and presentation)
- By the DOMS side calling an ssh-script to deliver a zip file of contents to Summa
- By the Summa side requesting latest changed objects via OAI-PMH
- By the DOMS side implementing the Summa API, through which Summa can request latest changes
The last option appears to be the most convenient for our use. Reason: The first would require more development on our part than the last. And the second is less convenient for Summa than the last. So, the last it is.
Overview of the work needed for Summa integration
The following is an overview of what work needs to be done by the different groups.
Methods needed in Summa integration component, as an implementation of the Summa storage API
We need an implementation of Summa's ReadableStorage interface, that is, the following methods
- getModificationTime(String base)
getRecord(String id, QueryOptions options)
getRecords(List of Strings id, QueryOptions options)
getRecordsModifiedAfter(long time, String base, QueryOptions options)
- next(long iteratorKey)
- next(long iteratorKey, int maxRecords)
See Summa Storage API javadoc at (where?)
Sequence diagrams showing the surroundings of the Summa Integration component:
Prerequisites and Assumptions