|
|
# 17-09-06 DB.nomics Technical Committee
|
|
|
# 17-09-06 DBnomics Technical Committee
|
|
|
|
|
|
## Attendees
|
|
|
Michel Juillard
|
|
|
Julien Lasselot
|
|
|
Thomas Brand
|
|
|
Bruno Duyé
|
|
|
Emmanuel Raviart
|
|
|
Christophe Benz
|
|
|
Johan Richer
|
|
|
Michel Juillard
|
|
|
Julien Lasselot
|
|
|
Thomas Brand
|
|
|
Bruno Duyé
|
|
|
Emmanuel Raviart
|
|
|
Christophe Benz
|
|
|
Johan Richer
|
|
|
|
|
|
## Agenda
|
|
|
- Full text search infrastructure
|
... | ... | @@ -38,18 +38,18 @@ Johan Richer |
|
|
- 3. **Development**: An issue item is assigned to a developer to complete scripts (downloader & converter), storage, indexation and finally display in the UI. Issue item moved to the next column to signal this step is finished.
|
|
|
- 4. **Validation**: Banque de France assign a person to an issue item for validation. The proper functioning of a fetcher should then be verified from end to end. This step can be discussed and decided during a Technical Committee Meeting. Issue item moved to the next column to signal the fetcher is officially finished.
|
|
|
- 5. **Closed**: List of finished fetchers.
|
|
|
- **Iterations** will be conducted weekly to pace the development of DB.nomics (UI, fetchers and all aspects of the product). An unformal meeting will take place every Monday at 2pm to conclude an iteration and briefly demonstrate the progress. A new iteration will be defined and published on the forum shortly after. Iteration duration may increase to 2 weeks depending on the velocity of the team.
|
|
|
- **Iterations** will be conducted weekly to pace the development of DBnomics (UI, fetchers and all aspects of the product). An unformal meeting will take place every Monday at 2pm to conclude an iteration and briefly demonstrate the progress. A new iteration will be defined and published on the forum shortly after. Iteration duration may increase to 2 weeks depending on the velocity of the team.
|
|
|
- **Technical Committee meetings**: They will take place every two weeks at Banque de France. Their purpose can be to share the progress made on fetchers during the previous iterations (validate them), as well as giving a preview of the current/next one.
|
|
|
- **Calendar**: Members of the Technical Committee will share their calendar with each other.
|
|
|
|
|
|
In addition, following today's discussion by email, we propose that communication between members of the Technical Committee should take place here on the DB.nomics forum, within the [Technical Committee category](https://forum.db.nomics.world/c/tech-com). Which, in the near future, should effectively function as a mailing list (working on it!).
|
|
|
In addition, following today's discussion by email, we propose that communication between members of the Technical Committee should take place here on the DBnomics forum, within the [Technical Committee category](https://forum.db.nomics.world/c/tech-com). Which, in the near future, should effectively function as a mailing list (working on it!).
|
|
|
|
|
|
### Technical
|
|
|
- **Missing values**: Fetchers never complete missing values in series. DB.nomics always store data "as is". This matter should be resolved at the API level.
|
|
|
- **Missing values**: Fetchers never complete missing values in series. DBnomics always store data "as is". This matter should be resolved at the API level.
|
|
|
- **Scheduler**: Publication dates should be parsed by the fetcher and stored in the metadata, when applicable (series, dataset, provider).
|
|
|
- **Storage**: Source data and JSON-transformed data are stored in Git repositories to keep history with one commit by fetcher pass.
|
|
|
|
|
|
## Next steps
|
|
|
- [Ongoing iteration](https://forum.db.nomics.world/t/20170911-iteration/87) to be concluded on Monday September
|
|
|
- [Ongoing iteration](https://forum.db.nomics.world/t/20170911-iteration/87) to be concluded on Monday September
|
|
|
11.
|
|
|
- Next Technical Committee meetings: Sept 15 and Sept 29. |
|
|
\ No newline at end of file |