[SeasonOfDocs] Introduction

Tue Jun 11 00:28:34 PDT 2019

Hi Byron,

Sorry for the late reply, I was on holidays last week.

All PR that you want to push, you can send me to review and maybe even push
it directly. Specially if it is something as straight forward as fixing
documentation and you see the PR stuck :)

I will get on track soon with what you are doing. If you need some guidance
on what to do or how to do it, don't hesitate to contact me directly,I will
try to help as much as I can.

Cheers,
María.

On Mon, Jun 10, 2019 at 1:29 AM Byron Cochrane <byron at openwork.nz> wrote:

> Thanks Jo,
>
> Yes, Metadata 101 sounds like a good home for the documentation for
> 19115-3 guidance.  What I am currently working on will more than likely
> need be generalised from the Aus/NZ point of view.  As we get further into
> that work over the next few months, we can sort that easy enough.
>
> I just submitted a pull request that should fix the “Edit in Github”
> problem.  That should simplify contributions a bit.  Will also look into
> how to correct the links to point at 3.6.x rather than 3.4.x which also
> often causes 404 errors.  Will think about a more elegant solution to
> that.  Guess I should submit an issue on that.
>
>
>
> Cheers,
> Byron Cochrane
>
> OpenWork Ltd
> Nelson, New Zealand
> byron at openwork.nz
> +64 21 794 501
> http://openwork.nz
>
>
>
> On 7/06/2019, at 8:23 PM, Jo Cook <jo.k.cook at gmail.com> wrote:
>
> Hi Byron,
>
> First things first- it's not currently all that easy to find the issues
> for the docs- which is something we should probably address. They are here:
> https://github.com/geonetwork/doc/issues
>
> Disclaimer- at present I'm probably the one person labelling up the
> issues- but my feeling is that those areas that you feel need improvement
> within the documentation (workflow, administration, additional schema
> plugins, harvesting, plugins and schema implementation) could all be
> flagged up as well- as something like "needs improvement". I'd be happy to
> see you submit a bunch of issues in for things like that, and then I will
> label them up. Is that something you could do without needing to spend too
> much time on it, given your work commitments?
>
> I don't know if this sounds like a plan as well, but with the schema
> documentation (ISO19115-3 guidance)- would metadata101.org be a good
> place for that to live?
>
> My first job, I think, is going to be to figure out who looks after the
> Readthedocs side of things so we can fix the "edit on github" links!
>
> Hope that makes sense,
>
> Jo
>
> On Wed, Jun 5, 2019 at 11:38 PM Byron Cochrane <byron at openwork.nz> wrote:
>
>> Hi Jo,
>>
>> All aboard with everything have suggested.
>> But where do I find the “easy to resolve”  issues you mention on the
>> GitHub site?  I am not seeing those.
>>
>> A bit about my current focus.  Besides being a general GeoNetwork
>> enthusiast and one of the most prolific implementers of this software in
>> the Oceana region,  I currently have a couple of projects underway that
>> relate well to this work.  The first is development of good practice
>> guidance for using ISO19115-3 in Australia and NZ.  GeoNetwork, being one
>> of the very few existing catalogues that support this standard is our
>> reference platform.  I would think a version of this document specific to
>> GN users could be useful.
>>
>> I am also aiding NIWA here in NZ in improving their cataloguing
>> capabilities.  This is based on GeoNetwork, but needs to tie in with other
>> catalogues as well. So issues around workflow, administration, additional
>> schema plugins, harvesting, etc. are all needed to be well documented.
>> Forefront here is good documentation on plugin schema support and
>> implementation.  These plugins have become pretty central to customisation
>> and have fallen badly behind in documentation, so that is where I would
>> like to put some initial focus.
>>
>> In general I found documentation to be the Achilles heel for may open
>> source projects.  Identifying what works to get good documentation is of
>> immense value to making a successful product.  At least in this part of the
>> world, GN has a mixed reputation.  The negative perceptions are largely
>> around the view that it is too complex.  Good documentation could help.  I
>> think of GeoNetwork as a software stack of which some parts are useful to
>> some installs and some parts will not be.  Documentation that describes
>> this stack in a way that organisations can understand how to make best use
>> of the different components of this stack would be extremely useful.
>>
>> Unless I can tie some of this directly to paid work, putting in more than
>> 4-6 hours a week to this effort will be a struggle, but I will do what I
>> can.  I may be able to leverage some time from my business partner as well.
>>
>> So how do we proceed?
>>
>> Cheers,
>> Byron Cochrane
>> <openwork_favicon__white96x96.png>
>>
>> OpenWork Ltd
>> Nelson, New Zealand
>> byron at openwork.nz
>> +64 21 794 501
>> http://openwork.nz
>>
>>
>>
>> On 5/06/2019, at 9:00 PM, Jo Cook <jo.k.cook at gmail.com> wrote:
>>
>> Hi Bryan,
>>
>> Great to have another Geonetwork person on board! Have you seen our
>> (myself and Maria's) ideas for what to do for Geonetwork at
>> https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#GeoNetwork? Feel
>> free to add/adjust as you see fit. I did send a message asking for
>> suggestions/contributions on the geonetwork mailing list but got no
>> response unfortunately.
>>
>> All the best
>>
>> Jo
>>
>> On Tue, Jun 4, 2019 at 11:40 PM Byron Cochrane <byron at openwork.nz> wrote:
>>
>>> Hello,
>>>
>>> My name is Byron Cochrane.  I am a long time GeoNetwork implementor and
>>> developer and very interested in improving GeoNetwork documentation.
>>> Currently have my own independent consultancy in New Zealand in which
>>> GeoNetwork and Metadata . Contributing to metadata guidance comprise the
>>> majority of our work at present.
>>>
>>> I have a long history of involvement in standardisation and cataloguing
>>> going back to 1994. This includes deep involvement in regional and
>>> international standards organisations including ANZLIC, ICSM, ISO TC 211,
>>> OGC and W3C. I have contributed to numerous international standards
>>> documents, testbeds and interoperability experiments including W3C Spatial
>>> Data on the Web Best Practices, Environmental Linked Features
>>> Interoperability Experiment (OGC), and numerous others.
>>>
>>> I have been an implementer and developer of GeoNetwork in Oceana and
>>> supporter of open source many years. Current relevant projects include
>>> the development of guidance for the implementation of ISO 19115-3 in the
>>> Oceana region and consolidated immigration and implementation of GeoNetwork
>>> 3.6 for a large national agency. I am very interested in helping improve
>>> GeoNetwork documentation.  Much of our current work requires this and the
>>> more integrated and sharable with other efforts the better.
>>>
>>> Cheers.
>>> Byron Cochrane
>>> <openwork_favicon__white96x96.png>
>>>
>>> OpenWork Ltd
>>> Nelson, New Zealand
>>> byron at openwork.nz
>>> +64 21 794 501
>>> http://openwork.nz
>>>
>>>
>>>
>>> _______________________________________________
>>> SeasonOfDocs mailing list
>>> SeasonOfDocs at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>>>
>>
>>
>> --
>> ------------------------
>> http://about.me/jocook
>>
>>
>>
>
> --
> ------------------------
> http://about.me/jocook
>
>
> _______________________________________________
> SeasonOfDocs mailing list
> SeasonOfDocs at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/seasonofdocs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/seasonofdocs/attachments/20190611/4ce8bf60/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openwork_favicon__white96x96.png
Type: image/png
Size: 1113 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/seasonofdocs/attachments/20190611/4ce8bf60/attachment.png>