Activity
From Dec 18, 2018 to Jan 16, 2019
Jan 16, 2019
-
04:35 PM Bug #13160 (Closed): European Commission missing code as management entity
- Management Body/Authority(ies) Code: authority:NAT:-, System: unk, Name: European Commission
Record URL: http://da...
Jan 14, 2019
-
12:35 PM Task #12861: Purge old records of the public GRSF Catalogue
- I checked the GRSF VRE, groups are now available for source databases (ram, firms, fishsource) and also record pages ...
Jan 11, 2019
-
11:39 AM Task #12861 (Closed): Purge old records of the public GRSF Catalogue
- All the records (597 in number) in GRSF have been updated.
-
11:38 AM Task #13098 (Closed): Update GRSF records in GRSF VRE
- All (597) the records have been updated
Jan 09, 2019
Jan 08, 2019
-
12:43 PM Task #12861: Purge old records of the public GRSF Catalogue
- As far as I remember we did not have any issues with updates.
However, it is fine by me to add an idle period betwe... -
12:05 PM Task #12861: Purge old records of the public GRSF Catalogue
- Hi Yannis,
the publishing rate should be limited to avoid failures on async operations caused by workloads.
Costa...
Jan 07, 2019
-
09:21 AM Task #13098 (Closed): Update GRSF records in GRSF VRE
- The approved records in GRSF VRE are missing information about the sources they are derived from (i.e. FIRMS, RAM, Fi...
-
09:17 AM Task #12861: Purge old records of the public GRSF Catalogue
- Hi Luca. Thanks a lot.
What exactly do you mean with the following?
Luca Frosini wrote:
> Please be sure that the...
Dec 28, 2018
-
04:18 PM Task #12861: Purge old records of the public GRSF Catalogue
- The new feature is available in the production instance.
@marketak@ics.forth.gr you can update the records when you ...
Dec 21, 2018
-
04:26 PM Task #12861: Purge old records of the public GRSF Catalogue
- I thought it would create issues if the field name is the same.
Since it does not, then use ***database_sources***. ... -
03:35 PM Task #12861: Purge old records of the public GRSF Catalogue
- Yannis Marketakis wrote:
> So in that case, the field name should be different. Right?
It could. But if it is eas... -
03:10 PM Task #12861: Purge old records of the public GRSF Catalogue
- So in that case, the field name should be different. Right?
-
03:02 PM Task #12861: Purge old records of the public GRSF Catalogue
- Yannis Marketakis wrote:
> @@luca.frosini@isti.cnr.it we already have this feature when publishing records in the GR...
Dec 19, 2018
-
11:43 AM Task #12861: Purge old records of the public GRSF Catalogue
- @@luca.frosini@isti.cnr.it we already have this feature when publishing records in the GRSF_Admin (in particular when...
-
11:09 AM Task #12861: Purge old records of the public GRSF Catalogue
- I Understand this is an additional information added in the json of the grsf record, so at worst it won't be used in ...
-
11:04 AM Task #12861: Purge old records of the public GRSF Catalogue
- The solution is ok for me.
Please take into account that this behaviour will occur also on GRSF_Admin VREfor any re...
Dec 18, 2018
-
11:09 AM Task #12861: Purge old records of the public GRSF Catalogue
- I am OK with that.
Technically speaking this means that we should include the database sources in the JSON serial... -
10:56 AM Task #12861: Purge old records of the public GRSF Catalogue
- Thanks to all, appreciated. I discussed the matter also with Anton and I showed him also the citation aspect. We thin...
-
09:43 AM Task #12861: Purge old records of the public GRSF Catalogue
- Thanks for your answers Lino. See some comments below:
Pasquale Pagano wrote:
> Waiting for @aureliano.gentile@fa... -
09:33 AM Task #12861: Purge old records of the public GRSF Catalogue
- Waiting for @aureliano.gentile@fao.org, please see below my personal opinion.
> The alternatives I see are:
>
... -
09:11 AM Task #12861: Purge old records of the public GRSF Catalogue
- I do not see any technical difficulties here. It is clearly a matter of decision.
I would expect that colleagues ...
Also available in: Atom