-
Weibel, S.L.: Border crossings : reflections on a decade of metadata consensus building (2005)
0.02
0.023864077 = product of:
0.047728155 = sum of:
0.047728155 = product of:
0.09545631 = sum of:
0.09545631 = weight(_text_:publishing in 1187) [ClassicSimilarity], result of:
0.09545631 = score(doc=1187,freq=4.0), product of:
0.250088 = queryWeight, product of:
4.885643 = idf(docFreq=907, maxDocs=44218)
0.051188353 = queryNorm
0.38169086 = fieldWeight in 1187, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
4.885643 = idf(docFreq=907, maxDocs=44218)
0.0390625 = fieldNorm(doc=1187)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Abstract
- In June of this year, I performed my final official duties as part of the Dublin Core Metadata Initiative management team. It is a happy irony to affix a seal on that service in this journal, as both D-Lib Magazine and the Dublin Core celebrate their tenth anniversaries. This essay is a personal reflection on some of the achievements and lessons of that decade. The OCLC-NCSA Metadata Workshop took place in March of 1995, and as we tried to understand what it meant and who would care, D-Lib magazine came into being and offered a natural venue for sharing our work. I recall a certain skepticism when Bill Arms said "We want D-Lib to be the first place people look for the latest developments in digital library research." These were the early days in the evolution of electronic publishing, and the goal was ambitious. By any measure, a decade of high-quality electronic publishing is an auspicious accomplishment, and D-Lib (and its host, CNRI) deserve congratulations for having achieved their goal. I am grateful to have been a contributor. That first DC workshop led to further workshops, a community, a variety of standards in several countries, an ISO standard, a conference series, and an international consortium. Looking back on this evolution is both satisfying and wistful. While I am pleased that the achievements are substantial, the unmet challenges also provide a rich till in which to cultivate insights on the development of digital infrastructure.
-
Miller, E.: ¬An introduction to the Resource Description Framework (1998)
0.02
0.023624228 = product of:
0.047248457 = sum of:
0.047248457 = product of:
0.09449691 = sum of:
0.09449691 = weight(_text_:publishing in 1231) [ClassicSimilarity], result of:
0.09449691 = score(doc=1231,freq=2.0), product of:
0.250088 = queryWeight, product of:
4.885643 = idf(docFreq=907, maxDocs=44218)
0.051188353 = queryNorm
0.37785465 = fieldWeight in 1231, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.885643 = idf(docFreq=907, maxDocs=44218)
0.0546875 = fieldNorm(doc=1231)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Abstract
- The Resource Description Framework (RDF) is an infrastructure that enables the encoding, exchange and reuse of structured metadata. RDF is an application of XML that imposes needed structural constraints to provide unambiguous methods of expressing semantics. RDF additionally provides a means for publishing both human-readable and machine-processable vocabularies designed to encourage the reuse and extension of metadata semantics among disparate information communities. The structural constraints RDF imposes to support the consistent encoding and exchange of standardized metadata provides for the interchangeability of separate packages of metadata defined by different resource description communities.
-
Broughton, V.: Automatic metadata generation : Digital resource description without human intervention (2007)
0.02
0.020805946 = product of:
0.04161189 = sum of:
0.04161189 = product of:
0.08322378 = sum of:
0.08322378 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
0.08322378 = score(doc=6048,freq=2.0), product of:
0.1792529 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.051188353 = queryNorm
0.46428138 = fieldWeight in 6048, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.09375 = fieldNorm(doc=6048)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Date
- 22. 9.2007 15:41:14
-
Wallis, R.; Isaac, A.; Charles, V.; Manguinhas, H.: Recommendations for the application of Schema.org to aggregated cultural heritage metadata to increase relevance and visibility to search engines : the case of Europeana (2017)
0.02
0.01687445 = product of:
0.0337489 = sum of:
0.0337489 = product of:
0.0674978 = sum of:
0.0674978 = weight(_text_:publishing in 3372) [ClassicSimilarity], result of:
0.0674978 = score(doc=3372,freq=2.0), product of:
0.250088 = queryWeight, product of:
4.885643 = idf(docFreq=907, maxDocs=44218)
0.051188353 = queryNorm
0.26989618 = fieldWeight in 3372, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.885643 = idf(docFreq=907, maxDocs=44218)
0.0390625 = fieldNorm(doc=3372)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Abstract
- Europeana provides access to more than 54 million cultural heritage objects through its portal Europeana Collections. It is crucial for Europeana to be recognized by search engines as a trusted authoritative repository of cultural heritage objects. Indeed, even though its portal is the main entry point, most Europeana users come to it via search engines. Europeana Collections is fuelled by metadata describing cultural objects, represented in the Europeana Data Model (EDM). This paper presents the research and consequent recommendations for publishing Europeana metadata using the Schema.org vocabulary and best practices. Schema.org html embedded metadata to be consumed by search engines to power rich services (such as Google Knowledge Graph). Schema.org is an open and widely adopted initiative (used by over 12 million domains) backed by Google, Bing, Yahoo!, and Yandex, for sharing metadata across the web It underpins the emergence of new web techniques, such as so called Semantic SEO. Our research addressed the representation of the embedded metadata as part of the Europeana HTML pages and sitemaps so that the re-use of this data can be optimized. The practical objective of our work is to produce a Schema.org representation of Europeana resources described in EDM, being the richest as possible and tailored to Europeana's realities and user needs as well the search engines and their users.
-
Farney, T.: using Google Tag Manager to share code : Designing shareable tags (2019)
0.02
0.01687445 = product of:
0.0337489 = sum of:
0.0337489 = product of:
0.0674978 = sum of:
0.0674978 = weight(_text_:publishing in 5443) [ClassicSimilarity], result of:
0.0674978 = score(doc=5443,freq=2.0), product of:
0.250088 = queryWeight, product of:
4.885643 = idf(docFreq=907, maxDocs=44218)
0.051188353 = queryNorm
0.26989618 = fieldWeight in 5443, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
4.885643 = idf(docFreq=907, maxDocs=44218)
0.0390625 = fieldNorm(doc=5443)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Abstract
- Sharing code between libraries is not a new phenomenon and neither is Google Tag Manager (GTM). GTM launched in 2012 as a JavaScript and HTML manager with the intent of easing the implementation of different analytics trackers and marketing scripts on a website. However, it can be used to load other code using its tag system onto a website. It's a simple process to export and import tags facilitating the code sharing process without requiring a high degree of coding experience. The entire process involves creating the script tag in GTM, exporting the GTM content into a sharable export file for someone else to import into their library's GTM container, and finally publishing that imported file to push the code to the website it was designed for. This case study provides an example of designing and sharing a GTM container loaded with advanced Google Analytics configurations such as event tracking and custom dimensions for other libraries using the Summon discovery service. It also discusses processes for designing GTM tags for export, best practices on importing and testing GTM content created by other libraries and concludes with evaluating the pros and cons of encouraging GTM use.
-
Understanding metadata (2004)
0.01
0.01387063 = product of:
0.02774126 = sum of:
0.02774126 = product of:
0.05548252 = sum of:
0.05548252 = weight(_text_:22 in 2686) [ClassicSimilarity], result of:
0.05548252 = score(doc=2686,freq=2.0), product of:
0.1792529 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.051188353 = queryNorm
0.30952093 = fieldWeight in 2686, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.0625 = fieldNorm(doc=2686)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Date
- 10. 9.2004 10:22:40
-
Sewing, S.: Bestandserhaltung und Archivierung : Koordinierung auf der Basis eines gemeinsamen Metadatenformates in den deutschen und österreichischen Bibliotheksverbünden (2021)
0.01
0.010402973 = product of:
0.020805946 = sum of:
0.020805946 = product of:
0.04161189 = sum of:
0.04161189 = weight(_text_:22 in 266) [ClassicSimilarity], result of:
0.04161189 = score(doc=266,freq=2.0), product of:
0.1792529 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.051188353 = queryNorm
0.23214069 = fieldWeight in 266, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.046875 = fieldNorm(doc=266)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Date
- 22. 5.2021 12:43:05
-
Roy, W.; Gray, C.: Preparing existing metadata for repository batch import : a recipe for a fickle food (2018)
0.01
0.0086691445 = product of:
0.017338289 = sum of:
0.017338289 = product of:
0.034676578 = sum of:
0.034676578 = weight(_text_:22 in 4550) [ClassicSimilarity], result of:
0.034676578 = score(doc=4550,freq=2.0), product of:
0.1792529 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.051188353 = queryNorm
0.19345059 = fieldWeight in 4550, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.0390625 = fieldNorm(doc=4550)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Date
- 10.11.2018 16:27:22
-
Baker, T.: ¬A grammar of Dublin Core (2000)
0.01
0.006935315 = product of:
0.01387063 = sum of:
0.01387063 = product of:
0.02774126 = sum of:
0.02774126 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
0.02774126 = score(doc=1236,freq=2.0), product of:
0.1792529 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.051188353 = queryNorm
0.15476047 = fieldWeight in 1236, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03125 = fieldNorm(doc=1236)
0.5 = coord(1/2)
0.5 = coord(1/2)
- Date
- 26.12.2011 14:01:22
