adiwg-mdtranslator 2.0.0rc3 → 2.0.0rc4

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 1b34a86163000468f677f4bf2b9ec4d99ac7a3b7
4
- data.tar.gz: ab59fc169dd40eae67f85cdc18435da669c213ad
3
+ metadata.gz: 9ac02a8bc57a59eda7e2f4c0a2580d05ba8954c1
4
+ data.tar.gz: 27b65f59348f2b77f436897178310970dbd166aa
5
5
  SHA512:
6
- metadata.gz: 2544e744a8a65c009ffd123072828077757d49cc96d711e03ed5279a1d5e014396578f6df74d13e1cdaf5051f17edf66aec3f87279f6e2a599f35e1b714198b2
7
- data.tar.gz: c8d2661db5830556659a2c938618d763a8e44a90facbbc1ce2c810b5801c723d321a4039faade0dd7a0bb104e05f968f85b289a08f0bdec3441b8e7f94c59792
6
+ metadata.gz: 2b49937387fec483647adf0e79d151558839e1642ae48606e2dc8bb7f1dc2d7c8984bcbe8e62b6c731ab448a645fd764ed3095d01f9d768502f027eb31e1a9e4
7
+ data.tar.gz: ed6261e0c4aa8c81854ca9754f3cdfe794d15f5342070b8ebaf01a557a8a541d0cf59e64b02c667fd88b675329103781f80b2392ca7611b22d72907a4373f3bc
data/Rakefile CHANGED
@@ -9,6 +9,7 @@ Rake::TestTask.new do |t|
9
9
  'test/writers/iso19110/tc*.rb',
10
10
  'test/writers/mdJson/tc*.rb',
11
11
  'test/writers/sbJson/tc*.rb',
12
+ 'test/writers/html/tc*.rb',
12
13
  'test/translator/tc*.rb'
13
14
  ]
14
15
  t.verbose = true
@@ -33,7 +33,7 @@ Gem::Specification.new do |spec|
33
33
  spec.add_runtime_dependency "thor", "~> 0.19"
34
34
  spec.add_runtime_dependency "uuidtools", "~> 2.1"
35
35
  spec.add_runtime_dependency "json-schema", "~> 2.7"
36
- spec.add_runtime_dependency "adiwg-mdjson_schemas", ">= 2.1.1"
36
+ spec.add_runtime_dependency "adiwg-mdjson_schemas", ">= 2.1.2"
37
37
  spec.add_runtime_dependency "adiwg-mdcodes", "~> 2.1"
38
38
  spec.add_runtime_dependency "jbuilder", "~> 2.5"
39
39
 
@@ -7,7 +7,16 @@
7
7
 
8
8
  ### Reader for ADIwg JSON metadata format (mdJson)
9
9
 
10
- The mdJson format is a simple JSON format for documenting and exchanging information about scientific projects and data. The Alaska Data Integration working group (ADIwg) wrote the standard to support translation to complex standards such as the ISO 19115-2 Geographic Metadata standard and FGDC's Content Standard for Digital Geospatial Metadata. The mdJson standard remains independent of any published standards while comprehensive enough to support translation to established standards. The mdJson record is also a convenient format to exchange directly with other organizations as the JSON structure is easily created and ingest by programming languages.
10
+ The mdJson format is a simple JSON format for documenting and
11
+ exchanging information about scientific projects and data.
12
+ The Alaska Data Integration working group (ADIwg) wrote the standard
13
+ to support translation to complex standards such as the ISO 19115-2
14
+ Geographic Metadata standard and FGDC's Content Standard for Digital
15
+ Geospatial Metadata. The mdJson standard remains independent of any
16
+ published standards while comprehensive enough to support translation
17
+ to established standards. The mdJson record is also a convenient format
18
+ to exchange directly with other organizations as the JSON structure
19
+ is easily created and ingest by programming languages.
11
20
 
12
21
  The mdJson format is fully documented on the interactive
13
22
  [mdTools](http://mdTools.adiwg.org) website.
@@ -1,14 +1,15 @@
1
1
  # adiwg mdTranslator / readers / mdJson
2
2
 
3
3
  # version 2 history
4
- # 2016-10-01 start of version 2
4
+ # 2.1.2 2017-05-19 deprecated iso topicCategory
5
+ # 2.0.0 2016-10-01 start of version 2
5
6
 
6
7
  module ADIWG
7
- module Mdtranslator
8
- module Readers
9
- module MdJson
10
- VERSION = "2.0.0"
11
- end
12
- end
13
- end
8
+ module Mdtranslator
9
+ module Readers
10
+ module MdJson
11
+ VERSION = "2.1.2"
12
+ end
13
+ end
14
+ end
14
15
  end
@@ -7,6 +7,12 @@
7
7
 
8
8
  ### Reader for ScienceBase JSON metadata format (sbJSON)
9
9
 
10
- The ScienceBase Item core is based on the Dublin Core Metadata Element Set but also includes other elements that may or may not be associated with other metadata standards that are useful for the core attribution of ScienceBase items. It is used as a means to integrate across multiple metadata standards, conventions, and practices in describing a wide array of scientific data and information assets important to science teams using ScienceBase.
10
+ The ScienceBase Item core is based on the Dublin Core Metadata
11
+ Element Set but also includes other elements that may or may not
12
+ be associated with other metadata standards that are useful for the
13
+ core attribution of ScienceBase items. It is used as a means to
14
+ integrate across multiple metadata standards, conventions, and
15
+ practices in describing a wide array of scientific data and
16
+ information assets important to science teams using ScienceBase.
11
17
 
12
18
  The sbJSON format is fully documented on the [ScienceBase Confluence page](https://my.usgs.gov/confluence/display/sciencebase/ScienceBase+Information+Model).
@@ -1,6 +1,7 @@
1
1
  # adiwg mdTranslator
2
2
 
3
3
  # version 2 history
4
+ # 2.0.0rc4 2017-05-19 bump mdJson schema version to 2.1.2
4
5
  # 2.0.0rc3 2017-05-16 removed topicCategory from schema and manage as keyword
5
6
  # 2.0.0rc2 2017-04-21 removed inline CSS option from CLI
6
7
  # 2.0.0rc1 2017-04-09 release candidate 1
@@ -9,7 +10,7 @@
9
10
  module ADIWG
10
11
  module Mdtranslator
11
12
  # current mdtranslator version
12
- VERSION = "2.0.0rc3"
13
+ VERSION = "2.0.0rc4"
13
14
  end
14
15
  end
15
16
 
@@ -3,6 +3,13 @@
3
3
 
4
4
  ### Writer for HTML 'human-readable' output of metadata
5
5
 
6
- The HTML Metadata Record output from the mdTranslator is intended to be a human readable version of the metadata content read in by the translator. The HTML output does not attempt mimic any established metadata standard but remains agnostic in its presentation. The HTML metadata output will display the full content of the metadata record ingested by the mdTranslator while translation to established standards may not support all fields.
7
-
8
- The HTML output can be conveniently embedded in a users web page to present metadata content to visitors.
6
+ The HTML Metadata Record output from the mdTranslator is intended to
7
+ be a human readable version of the metadata content read in by the
8
+ translator. The HTML output does not attempt mimic any established
9
+ metadata standard but remains agnostic in its presentation.
10
+ The HTML metadata output will display the full content of the
11
+ metadata record ingested by the mdTranslator while translation to
12
+ established standards may not support all fields.
13
+
14
+ The HTML output can be conveniently embedded in a users web page to
15
+ present metadata content to visitors.
@@ -94,6 +94,12 @@ module ADIWG
94
94
  shortVersion = aShortVersion[0].to_s + '.' + aShortVersion[1].to_s
95
95
  @html.h1('mdTranslator ' + shortVersion + ' HTML Metadata Record', 'id' => 'mdtranslator-metadata-report')
96
96
 
97
+ # report date
98
+ @html.section(:class => 'block') do
99
+ @html.em('Report Generated:')
100
+ @html.text!(Time.new.inspect)
101
+ end
102
+
97
103
  # metadata source
98
104
  @html.h2('Metadata Source', 'id' => 'metadataSource')
99
105
  @html.section(:class => 'block') do
@@ -2,6 +2,7 @@
2
2
  # resource information
3
3
 
4
4
  # History:
5
+ # Stan Smith 2017-05-19 removed iso topicCategory (now presented as keywords)
5
6
  # Stan Smith 2017-03-25 refactored for mdTranslator 2.0
6
7
  # Stan Smith 2015-07-16 refactored to remove global namespace $HtmlNS
7
8
  # Stan Smith 2015-03-24 original script
@@ -282,19 +283,9 @@ module ADIWG
282
283
  @html.details do
283
284
  @html.summary('Keywords', {'id' => 'resourceInfo-keyword', 'class' => 'h3'})
284
285
  @html.section(:class => 'block') do
285
-
286
- # resource - topic categories []
287
- hResource[:topicCategories].each do |category|
288
- @html.em('Topic: ')
289
- @html.text!(category)
290
- @html.br
291
- end
292
-
293
- # resource - keywords []
294
286
  hResource[:keywords].each do |hKeyword|
295
287
  keywordClass.writeHtml(hKeyword)
296
288
  end
297
-
298
289
  end
299
290
  end
300
291
  end
@@ -3,6 +3,14 @@
3
3
 
4
4
  ### Writer for ISO 19110 Feature Catalogue
5
5
 
6
- The mdTranslator 'iso19110' writer implements about 70% of the for ISO 19110 standard. Efforts were made to include all elements of the ISO standard that describe entity-attribute descriptions for tabular data, spreadsheets, and relational databases.
6
+ The mdTranslator 'iso19110' writer implements about 70% of the for
7
+ ISO 19110 standard. Efforts were made to include all elements of the
8
+ ISO standard that describe entity-attribute descriptions for tabular
9
+ data, spreadsheets, and relational databases.
7
10
 
8
- The ISO 19110 record can be used to provide data dictionary information for ISO 19115-2 metadata (circa 2003) and is delivered as a separate file from the ISO 19115-2 resource metadata. This inconvenient implementation was improved in the 2014 revision ISO 19115-1 schema. mdTranslator will provide support for ISO 19115-1 sometime in 2017.
11
+ The ISO 19110 record can be used to provide data dictionary
12
+ information for ISO 19115-2 metadata (circa 2003) and is delivered
13
+ as a separate file from the ISO 19115-2 resource metadata. This
14
+ inconvenient implementation was improved in the 2014 revision I
15
+ SO 19115-1 schema. mdTranslator will provide support for ISO
16
+ 19115-1 sometime in 2017.
@@ -3,4 +3,10 @@
3
3
 
4
4
  ### Writer for ISO 19115-2:2009 Geographic Metadata
5
5
 
6
- The mdTranslator iso19115_2 writer implements approximately 95% of the for ISO 19115-2 standard. Efforts were made to include all elements of the ISO standard that support general data descriptions to ensure generation of health and robust project and data metadata records. The sections of 19115-2 not supported by the mdTranslator writer are the 'quantitative' section for data quality, portrayal catalog reference, and application schema information.
6
+ The mdTranslator iso19115_2 writer implements approximately 95% of
7
+ the for ISO 19115-2 standard. Efforts were made to include all
8
+ elements of the ISO standard that support general data descriptions
9
+ to ensure generation of health and robust project and data metadata
10
+ records. The sections of 19115-2 not supported by the mdTranslator
11
+ writer are the 'quantitative' section for data quality, portrayal
12
+ catalog reference, and application schema information.
@@ -7,7 +7,17 @@
7
7
 
8
8
  ### Writer for ADIwg JSON metadata format (mdJson)
9
9
 
10
- The mdJson format is a simple JSON format for documenting and exchanging information about scientific projects and data. The Alaska Data Integration working group (ADIwg) wrote the standard to support translation to complex standards such as the ISO 19115-2 Geographic Metadata standard and FGDC's Content Standard for Digital Geospatial Metadata. The mdJson standard remains independent of any published standards while comprehensive enough to support translation to established standards. The mdJson record is also a convenient format to exchange directly with other organizations as the JSON structure is easily created and ingest by programming languages.
10
+ The mdJson format is a simple JSON format for documenting and
11
+ exchanging information about scientific projects and data.
12
+ The Alaska Data Integration working group (ADIwg) wrote the
13
+ standard to support translation to complex standards such as
14
+ the ISO 19115-2 Geographic Metadata standard and FGDC's Content
15
+ Standard for Digital Geospatial Metadata. The mdJson standard
16
+ remains independent of any published standards while comprehensive
17
+ enough to support translation to many established standards.
18
+ The mdJson record is also a convenient format to exchange directly
19
+ with other organizations as the JSON structure is easily created
20
+ and ingest by modern programming languages.
11
21
 
12
22
  The mdJson format is fully documented on the interactive
13
23
  [mdTools](http://mdTools.adiwg.org) website.
@@ -7,6 +7,13 @@
7
7
 
8
8
  ### Writer for ScienceBase JSON metadata format (sbJSON)
9
9
 
10
- The ScienceBase Item core is based on the Dublin Core Metadata Element Set but also includes other elements that may or may not be associated with other metadata standards that are useful for the core attribution of ScienceBase items. It is used as a means to integrate across multiple metadata standards, conventions, and practices in describing a wide array of scientific data and information assets important to science teams using ScienceBase.
10
+ The ScienceBase Item core is based on the Dublin Core Metadata
11
+ Element Set but also includes other elements that may or may not
12
+ be associated with other metadata standards that are useful for
13
+ the core attribution of ScienceBase items. It is used as a means
14
+ to integrate across multiple metadata standards, conventions, and
15
+ practices in describing a wide array of scientific data and
16
+ information assets important to science teams using ScienceBase.
11
17
 
12
- The sbJSON format is fully documented on the [ScienceBase Confluence page](https://my.usgs.gov/confluence/display/sciencebase/ScienceBase+Information+Model).
18
+ The sbJSON format is fully documented on
19
+ the [ScienceBase Confluence page](https://my.usgs.gov/confluence/display/sciencebase/ScienceBase+Information+Model).
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: adiwg-mdtranslator
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.0rc3
4
+ version: 2.0.0rc4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Stan Smith
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2017-05-17 00:00:00.000000000 Z
12
+ date: 2017-05-21 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: bundler
@@ -129,14 +129,14 @@ dependencies:
129
129
  requirements:
130
130
  - - ">="
131
131
  - !ruby/object:Gem::Version
132
- version: 2.1.1
132
+ version: 2.1.2
133
133
  type: :runtime
134
134
  prerelease: false
135
135
  version_requirements: !ruby/object:Gem::Requirement
136
136
  requirements:
137
137
  - - ">="
138
138
  - !ruby/object:Gem::Version
139
- version: 2.1.1
139
+ version: 2.1.2
140
140
  - !ruby/object:Gem::Dependency
141
141
  name: adiwg-mdcodes
142
142
  requirement: !ruby/object:Gem::Requirement
@@ -610,7 +610,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
610
610
  version: 1.3.1
611
611
  requirements: []
612
612
  rubyforge_project:
613
- rubygems_version: 2.5.2
613
+ rubygems_version: 2.4.5
614
614
  signing_key:
615
615
  specification_version: 4
616
616
  summary: The mdtranslator (metadata translator) is a tool for translating metadata