Release INARA: Error: "This journal is too old"

Cougar

C
I wanted to build the history of my CMDR by uploading the logs to Inara. Since I have neglected the page so far, I have logs dating back to January 2017.

However, when I try to start from the first Log, I get an error message

"ERROR: This journal is too old."

Is there some hack how I can still reconstruct the full history, or is not possible anymore to import the old logs to Inara for some technical reason? Some alternative tool than Inara which can also import old logs?

Thanks.
 

Artie

Artie
Yes, there is a technical reason for it. Some data (like missions logs and flight logs) gets summarized to monthly overviews after some time to keep the database size on a reasonable level (and there is also usually no need to have such detailed records far in the past). Importing of older journals can lead to problems as any older records needs to be added to the summaries and any duplicate records will also skew the summaries (as there is not known if these records were present already or not). Maybe it will gets improved in the future with some limits, but using the famous words - "no ETA, no guarantees". ;)
 

Cougar

C
Ok, thanks - no problem.

Different topic: I linked INARA to EDMarketConnector, and stuff like ship details (modules etc). does not seem to be transferred, same with stored modules. However, my ships themselves appear just fine, and Material data was also auto-imported. EDMarketConnector can also export just fine to Coriolis, and I can import from there to Inara, but automating this would be nice.

Is there something I have to do to trigger the transfer of detailed ship data and stored modules from EDMarketConnector to INARA?
 

Artie

Artie
The ships loadouts and stored modules will be implemented on Inara with 3.0 release (as there is an additional stuff for it added in the journals). I am working on it right now. :)
 

Nitross

N
Mr.Hidden said:
Yes, there is a technical reason for it. Some data (like missions logs and flight logs) gets summarized to monthly overviews after some time to keep the database size on a reasonable level (and there is also usually no need to have such detailed records far in the past). Importing of older journals can lead to problems as any older records needs to be added to the summaries and any duplicate records will also skew the summaries (as there is not known if these records were present already or not). Maybe it will gets improved in the future with some limits, but using the famous words - "no ETA, no guarantees". ;)
Click to expand...

Tricky one to be sure; it's difficult to optimize ressource usage and allow for a complete log. As a Web Developer myself, I can sympathize.

Out of curiosity, have you already considered ideas along the following?
  • Having a "Full log" import option - that takes all the log files into consideration at once - that overrides the log instead of adding to it, re-creating "clean" summaries in doing so.
  • Keeping a list of imported logs so you can check if it is missing from the summary before adding the information.

For the first option, new improvements in HTML5 and JavaScript would allow you to do the work client side and avoid uploading all the files to the server. This would reduce the load on the server and produce the most accurate results. It might even be possible to make a web version of a live log viewer with this. However, it would mean rebuilding the server side "summarizing" code in JS for the client. It could simply be done server side but, even with only 410 hours of game play, my log is already 15 MB. With all the players, that makes a lot of data to receive.

The second option has the advantage of being more transparent for the user, as they would simply upload all the log files like they already do. It could also help reduce the load on the server by allowing a check to reject uploads of known files. However, it requires being able to "summarize" individual logs and add the difference to the current summary. Depending on how you work out summaries, that might not be possible...
 

Artie

Artie
Yes, EDSM is very nice tool, especially for the explorers, I can recommend it. :)


Nitross said:
Tricky one to be sure; it's difficult to optimize ressource usage and allow for a complete log. As a Web Developer myself, I can sympathize.

Out of curiosity, have you already considered ideas along the following?
  • Having a "Full log" import option - that takes all the log files into consideration at once - that overrides the log instead of adding to it, re-creating "clean" summaries in doing so.
  • Keeping a list of imported logs so you can check if it is missing from the summary before adding the information.

For the first option, new improvements in HTML5 and JavaScript would allow you to do the work client side and avoid uploading all the files to the server. This would reduce the load on the server and produce the most accurate results. It might even be possible to make a web version of a live log viewer with this. However, it would mean rebuilding the server side "summarizing" code in JS for the client. It could simply be done server side but, even with only 410 hours of game play, my log is already 15 MB. With all the players, that makes a lot of data to receive.

The second option has the advantage of being more transparent for the user, as they would simply upload all the log files like they already do. It could also help reduce the load on the server by allowing a check to reject uploads of known files. However, it requires being able to "summarize" individual logs and add the difference to the current summary. Depending on how you work out summaries, that might not be possible...
Click to expand...

Yep, there are multiple options how to do that. I was also briefly evaluating an option to provide some simple "dump" import format and let others to pre-process the data to reduce a load on processing a ton of records. But, to be honest, it is not a priority at this moment as there are much more important and beneficial things for the wider user base that should be done. ;)
 
You must log in or register to reply here.
Back
Top Bottom