<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi to all!<br>
<br>
I<font face="Helvetica, Arial, sans-serif"> haven’t notice that the
flag MODIFY_TOPICCATEGORY already existed.<br>
This flag at the moment only controls the change of the topic
categories via admin page but doesn’t control if a new topic
category can be added via metadata, as I described in my first
email.<br>
I will use this flag to control if the metadata can contain new
categories or not, returning <span style="color: rgb(64, 64,
64); font-size: 16px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 24px;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px; display:
inline ! important; float: none; background-color: rgb(252, 252,
252);"><code> 'the topic category/theme 'x' is invalid!' </code></span></font><span
style="color: rgb(64, 64, 64); font-family: Lato, proxima-nova,
'Helvetica Neue', Arial, sans-serif; font-size: 16px; font-style:
normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: 24px; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
display: inline !important; float: none; background-color:
rgb(252, 252, 252);"><code><font face="Helvetica, Arial,
sans-serif">if not.<br>
<br>
My doubt is what should be the default/initial value of the
flag ? </font> </code></span><br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
The implementation is almost complete I will make a pull request
soon. <br>
Regards,<br>
<br>
Eduardo Castanho<br>
<br>
IPMA<br>
Instituto Português do Mar e da Atmosfera<br>
Lisboa Portugal<br>
<br>
<div class="moz-cite-prefix">On 30-12-2015 21:43, Patrick Dufour
wrote:<br>
</div>
<blockquote
cite="mid:CAKv4CpojukqKM10dz3YoPUnsqfAoJ=yUrPPa9jLRasBQfDyXMw@mail.gmail.com"
type="cite">
<p dir="ltr">I agree that multiple categories set for a
resourcebase object should be possible.</p>
<p dir="ltr">Yes, with batch metadata editing, fixing by hand
shouldn't be difficult.</p>
<p dir="ltr">For the flag, how will GeoNode "know" the categories
are ISO. It's implied, since they are the only ones there by
default, but the flag wouldn't trigger an ISO check. It would
just check that the category currently exists or not.
Otherwise, we'd probably need another field in the Category
model to say whether each is ISO or not. Either option is
acceptable.</p>
<p dir="ltr">Regards,<br>
Patrick</p>
<div class="gmail_quote">On Dec 30, 2015 10:37 AM, "Eduardo
Castanho" <<a moz-do-not-send="true"
href="mailto:eduardo.castanho@ipma.pt">eduardo.castanho@ipma.pt</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi! Patrick<br>
<br>
In last day of the code sprint in Turin, we talked about the
lack of fields in Geonode metatada, comparing with ISO 19115
profile.<br>
One of those fields was Topic Category, that isn't fully
supported by Geonode, because it only accepts one, more
specifically the first topic category value on the metadata
file.<br>
<br>
Your suggestion seems fine to me, but it implies that if you
start with the flag on False and then change it to True, the
data that you have in Geonode will be inconsistent, for
example, the TopicCategory Model/Table will have non ISO
entries.<br>
Some sort of solution to minimize this can be implemented, but
in my opinion it only will bring an overload to the Geonode
and this can be easily managed by "hand".<br>
<br>
May be the name for the FLAG can be more explicit like
ISO_CATEGORIES_STRICT.<br>
<br>
<br>
Regards,<br>
<br>
Eduardo Castanho<br>
<br>
IPMA<br>
Instituto Português do Mar e da Atmosfera<br>
Lisboa Portugal<br>
<br>
<br>
<br>
<br>
On 29-12-2015 22:30, Patrick Dufour wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Good afternoon, Eduardo.<br>
<br>
Could you briefly recap the relevant discussion during the
sprint? I<br>
missed that conversation.<br>
<br>
That is the expected behavior. We wanted to be sure that if
you<br>
imported data from a source that isn't following that ISO
standard<br>
closely that the import will work rather than throwing an
error.<br>
GeoNode will match an existing category if possible and will
create a<br>
new category if needed.<br>
<br>
I think my preference is to maintain that existing "default"
behavior.<br>
However, I think a flag in settings like
"CATEGORIES_STRICT=False"<br>
would work. If CATEGORIES_STRICT is true, then if a
category doesn't<br>
match on upload/import an error is thrown. If
CATEGORIES_STRICT is<br>
false, then the existing behavior goes.<br>
<br>
Regards,<br>
Patrick<br>
<br>
On 12/29/15, Eduardo Castanho <<a moz-do-not-send="true"
href="mailto:eduardo.castanho@ipma.pt" target="_blank">eduardo.castanho@ipma.pt</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi!! to all<br>
<br>
I'm trying to implement multiple Topic Categories in
Geonode, so that<br>
the metadata is more according to ISO 19115, as was
discussed in this<br>
year code sprint.<br>
<br>
But I have a doubt about the correct behavior in the
upload of<br>
metadata that contains Topic Categories that doesn't
belong to ISO<br>
CodeList.<br>
<br>
Currently, Geonode creates a new category :<br>
<br>
elif key == 'topic_category':<br>
value, created =<br>
TopicCategory.objects*.get_or_create*(<br>
identifier=value.lower(),<br>
defaults={'description': '',<br>
'gn_description': value})<br>
key = 'category'<br>
defaults[key] = value<br>
<br>
<br>
@ geonode/geonode/layers/utils.py (line 442)/****/<br>
<br>
Is this the expected behavior?<br>
If we have multiple categories imported from metatada
files, the number<br>
of new categories will raise a lot (including spelling
errors), can this<br>
be bad ?<br>
<br>
with best regards,<br>
Eduardo Castanho<br>
<br>
IPMA<br>
Instituto Português do Mar e da Atmosfera<br>
Lisboa Portugal<br>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>