| 11 | | Every resource should have meta information, which consists of: |
| 12 | | * The author of the resource |
| 13 | | * The date the resource was created |
| 14 | | * Version of the resource |
| 15 | | * The date the resource was last modified |
| 16 | | * Who was the last that modified the resource |
| 17 | | * The dimensions of the image (if the target of the resource is an image) |
| 18 | | * etc. |
| | 11 | Sophie2 Server and the Client will use the same module for resources. |
| 21 | | * Get familiar with the resource concepts, described in [wiki:BASE_RESOURCE_COMMONS_R0]. |
| 22 | | * Look at [wiki:S2S_PERSIST_RESOURCES_R0] to understand how the resources will be stored on the server. |
| 23 | | * Discuss and decide how to store the meta information for every resource (for example, if resources are persisted in a database, their corresponding meta could be stored in a separate table). |
| 24 | | * In the persistence layer of the server, add functionality for dealing with meta information. |
| 25 | | * Write appropriate unit tests. |
| | 14 | * Get familiar with the resource concepts, described in [wiki:BASE_RESOURCE_COMMONS_R0]. Look at [wiki:S2S_PERSIST_RESOURCES_R0] to understand how the resources will be stored. |
| | 15 | * Design a model for persisting meta information on the server (probably, the same as in the client). Since this task is tightly connected with the BASE tasks about resources, it would be best to design them together. |
