search

federatedbookkeeping / timesheets

Federated Timesheets Project. Gitter: https://gitter.im/federatedbookkeeping/timesheets
MIT License
9 stars 1 forks source link

Import from various formats into WikiSuite (milestone 3a) #30

Closed michielbdejong closed 2 years ago

michielbdejong commented 2 years ago

See https://github.com/federatedbookkeeping/timesheets#milestone-3-wikisuite

kroky commented 2 years ago

Import from timeld.org gateway works on timesheet.dev3.evoludata.com via tabular 11: https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=11

mcalligator commented 2 years ago

Great news! OK, so I've checked the data exposed by that link, and it looks like there's a metadata mapping issue: a Tiki project seems to be mapped to a timeld timesheet, rather than project in timeld. I suspect this is also the root cause of data POSTed to timeld from Tiki (as in #31 ) not being visible in timeld.

Could you address the metadata mismatch and try the import again? I've updated a number of the entries in that particular timesheet (ts-agm-2022-08-08), so it'll be evident when the data refresh has occurred.

kroky commented 2 years ago

In fact, this is done on purpose. We don't track timesheet records internally in Tiki, so I have to artificially create them. We discussed with @gsvarovsky that I can use user/project as the timesheet identifier and that's what I do. The integration currently uses fedb/fedt as the project and refers to different Tiki projects as timesheets. Do you see an issue using this approach? Not sure why the data is not visible in timeld but it is definitely accepted via the timeld API.

kroky commented 2 years ago

Milestone 3a has been completed. Demonstration could be done via 2 ways:

  1. Install Tiki (https://tiki.org/Get-Tiki), Install Timesheets profile (https://profiles.tiki.org/Timesheets), configure DSN/Content authentication with your credentials for pondersource and timeld. Configure tabular formats for Mite, Scoro and Time with proper API endpoints depending on your accounts in these 3rd parties. Add local Tiki users for all the users you plan to import data for.
  2. This is what has been done in https://timesheet.dev3.evoludata.com - you can register and use the existing tabular formats there.

Usage:

  1. manual import using Import button in existing tabulars in the following formats: 1.1. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=6 - Full format using the WikiSuite/Tiki timesheet format. 1.2. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=7 - csv format for Time app 1.3. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=8 - json format using the Scoro API 1.4. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=9 - json format using the Mite API 1.5. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=10 - json format using the Pondersource/Prejournal API 1.6. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=11 - ndjson format using the timeld API 1.7. https://timesheet.dev3.evoludata.com/tiki-tabular-list?tabularId=12 - iCal/ics format for calendar synchronization
  2. automated import using Tiki Scheduler - a job could be scheduled to run on a specific interval and does the import in an automated way. 1.5. and 1.6. import require parameters (worker/user and project), so distinct import jobs need to be configured for distinct users/projects.