I would like to propose an extension to allow wiki markup to be used in (some elements) of metadata. By default markup is disabled but can be enabled by the Administrator system-wide. When enabled the marked up text is rendered in search results and when viewing metadata.
+1 for me Jesse, I’ve seen some metadata records using HTML for styling which may be more complex to deal with (for indexing, layout).
Wiki syntax sounds like a good choice for basic styling without problem for indexing.
I would like to propose an extension to allow wiki markup to be used in (some elements) of metadata. By default markup is disabled but can be enabled by the Administrator system-wide. When enabled the marked up text is rendered in search results and when viewing metadata.
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
I don't have any problem with the overall idea of this as formatting certainly helps when trying to understand what is being said by the metadata.
I did have some initial concerns about sites not wanting this markup in there but presumably the reason that wiki markup is being used is that even without any parsing and presentation by the wiki markup classes, it is still quite effective (considerably better than none at all and better than html which may not look anything like the final result from an html presentation engine).
Cheers,
Simon
PS: I'm having trouble parsing and understanding the last two sentences in the fourth paragraph of the proposal section - can you expand a little on what you mean there so I can better understand the implications? Do you mean config.xml in the second last sentence?
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Thursday, 22 November 2012 5:34 PM
To: Devel geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] CFV: Wiki render wiki syntax in metadata
I would like to propose an extension to allow wiki markup to be used in (some elements) of metadata. By default markup is disabled but can be enabled by the Administrator system-wide. When enabled the marked up text is rendered in search results and when viewing metadata.
If Site B harvest data from Site A which has the Wiki markup - will the
markup be removed during the harvest or will Site B end up displaying wiki
markup (assuming site b does not support wiki markup)
Just wondering if this is going to cause issues with the harvesting....
I have recently been thinking about this issue as well. I see a couple options:
Render it before export and have the download have html in the text
Remove the wiki syntax
Keep the syntax
I think in most cases the syntax should be removed but perhaps it is worth having this be a configuration option so the administrator can decide how to handle this given their system.
I don’t want to add services to get Metadata without wiki syntax because that would complicate the API for a specific use-case.
If Site B harvest data from Site A which has the Wiki markup - will the
markup be removed during the harvest or will Site B end up displaying wiki
markup (assuming site b does not support wiki markup)
Just wondering if this is going to cause issues with the harvesting…
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
I have recently been thinking about this issue as well. I see a couple
options:
1. Render it before export and have the download have html in the text
2. Remove the wiki syntax
3. Keep the syntax
I think in most cases the syntax should be removed but perhaps it is worth
having this be a configuration option so the administrator can decide how
to handle this given their system.
I have been tested harvesting on some catalogs providing HTML in the
ISO19139 and it was not filtered by the server - and GeoNetwork takes care
of it more or less. I also know some user who would like to preserve wiki
syntax during harvesting. So a configuration option could be good.
Francois
I don't want to add services to get Metadata without wiki syntax because
that would complicate the API for a specific use-case.
Jesse
On Mon, Nov 26, 2012 at 4:59 PM, ianwallen <ianwallen@anonymised.com> wrote:
I have a quick question regarding the harvesting.
If Site B harvest data from Site A which has the Wiki markup - will the
markup be removed during the harvest or will Site B end up displaying wiki
markup (assuming site b does not support wiki markup)
Just wondering if this is going to cause issues with the harvesting....
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
I have updated the proposal to take into account exporting the metadata as well as harvesting. There is a couple new paragraphs at the end of the proposal that explain the export configuration options.
I have recently been thinking about this issue as well. I see a couple options:
Render it before export and have the download have html in the text
Remove the wiki syntax
Keep the syntax
I think in most cases the syntax should be removed but perhaps it is worth having this be a configuration option so the administrator can decide how to handle this given their system.
I have been tested harvesting on some catalogs providing HTML in the ISO19139 and it was not filtered by the server - and GeoNetwork takes care of it more or less. I also know some user who would like to preserve wiki syntax during harvesting. So a configuration option could be good.
Francois
I don’t want to add services to get Metadata without wiki syntax because that would complicate the API for a specific use-case.
Jesse
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
If Site B harvest data from Site A which has the Wiki markup - will the
markup be removed during the harvest or will Site B end up displaying wiki
markup (assuming site b does not support wiki markup)
Just wondering if this is going to cause issues with the harvesting…
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
If Site B harvest data from Site A which has the Wiki markup - will the
markup be removed during the harvest or will Site B end up displaying wiki
markup (assuming site b does not support wiki markup)
Just wondering if this is going to cause issues with the harvesting…
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov