Activity
From May 26, 2019 to Jun 24, 2019
Jun 24, 2019
-
10:52 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- thanks, the week-end contributed to the full recovery ;-)
Regarding the short name, the dominant record is the one...
Jun 21, 2019
-
03:42 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Hi Aureliano,
I hope you are better and have recovered.
Indeed, the URL of the record is https://bluebridge.d4sc...
Jun 20, 2019
-
12:03 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Hi Yannis, my apologies for the delayed answer but I was sick the last few days.
I checked https://ckan-grsf-admin2....
Jun 13, 2019
-
03:56 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- I've triggered the workflow for merging the first two GRSF Stock records. The result is https://ckan-grsf-admin2.d4sc...
-
03:09 PM Bug #16923 (Closed): Cannot publish records in GRSF Admin VRE (unauthorized)
- Thanks for the update Francesco. It's fine now. I published a record properly.
-
02:48 PM Bug #16923: Cannot publish records in GRSF Admin VRE (unauthorized)
- Hi @marketak@ics.forth.gr,
the issue could be caused by a patch recently released to the CKAN APIs.
I just disabl... -
02:20 PM Bug #16923: Cannot publish records in GRSF Admin VRE (unauthorized)
- I just tried. Still the same issue.
Jun 12, 2019
-
04:58 PM Bug #16923 (In Progress): Cannot publish records in GRSF Admin VRE (unauthorized)
- Can you please retry now?
-
03:33 PM Bug #16923 (Closed): Cannot publish records in GRSF Admin VRE (unauthorized)
- I tried to publish a record in GRSF Admin today and encountered a not authorized message. The detailed message is sho...
-
12:06 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- I think as a temporary rule, the "dominant" record is the one providing all and only the codes for the semantic ident...
-
11:42 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- In addition:
* should we apply this rule (about the dominant record) only for the semantic ID, or we should apply... -
11:29 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Yes that would be an option.
I'll record this (in fact I'll create a wiki page with the workflow for the merging) a... -
10:34 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Thanks, solution 2 is pretty logic but then other factors drive the choice. For example for iattc and iccat, in place...
Jun 11, 2019
-
04:12 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- For the moment and as regards the records under merging that are described in this issue we could move on by manually...
-
02:40 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Thanks Yannis.
In the example you provided there is indeed one of the main issue of the merge process: the merge i... -
10:32 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Thanks for the confirmation Aureliano.
One more clarification. I ran the merging process for the first case shown ...
Jun 10, 2019
-
05:21 PM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Thanks Yannis,
Yes you are right, let's try to clarify and to identify operational rules.
In case of merging tw... -
09:50 AM Task #16880 (In Progress): Merge GRSF records (FIRMS - IOTC vs RAM)
-
09:48 AM Task #16880: Merge GRSF records (FIRMS - IOTC vs RAM)
- Before moving on with the actual merging, please clarify what do you mean with UUID (I suspect you are referring to S...
Jun 05, 2019
-
04:05 PM Task #16880 (Closed): Merge GRSF records (FIRMS - IOTC vs RAM)
- Dear colleagues, to make progress on **GRSF records merge action** I make this ticket to request the merge of a few r...
Also available in: Atom