Project:Principles - Revision history

Harej: Creating sections

2023-07-11T02:01:30Z

Creating sections

← Older revision		Revision as of 02:01, 11 July 2023
Line 1:		Line 1:
	~~'''~~Librarybase~~'''~~ is a project to build a database of metadata together as a community. It is inspired by projects like Wikidata and OpenAlex, but differs from both in certain respects.		Librarybase is a project to build a database of metadata together as a community. It is inspired by projects like Wikidata and OpenAlex, but differs from both in certain respects.

	'''~~Librarybase is a staging ground~~'''~~. Some entries are from bulk imports~~ of ~~middling quality. Others are efforts~~ to ~~assign persistent identifiers to works that otherwise never had them. This is~~ a project ~~that will improve incrementally. We have to start somewhere~~.		These are the '''principles''' of Librarybase, based on an essay written by [[User:Harej]] in May 2023, but intended to be a living document representing the values and motivations of the project's community as it grows, amendable by [[Project:Consensus\|consensus]].

	~~'''~~Librarybase ~~improves on existing data'''~~. ~~Librarybase does not seek~~ to ~~create yet another open dataset of clean academic publication metadata~~. ~~While~~ that ~~is definitely part of it, it is just our starting point~~. ~~The value Librarybase brings is not from repeating what projects like OpenAlex already do, but by ''expanding'' on it, through integration with the Wikidata graph and through additions by contributors~~.		==Librarybase is a staging ground==
			Some entries are from bulk imports of middling quality. Others are efforts to assign persistent identifiers to works that otherwise never had them. This is a project that will improve incrementally. We have to start somewhere.

	~~'''~~Librarybase ~~connects databases together'''. Much like Wikidata,~~ Librarybase ~~seeks~~ to ~~connect the various providers~~ of publication metadata. ~~Different industries have different standards for identifying documents~~, ~~and~~ Librarybase brings ~~them together under its flexible data model and common ontology~~ with Wikidata.		==Librarybase improves on existing data==
			Librarybase does not seek to create yet another open dataset of clean academic publication metadata. Such metadata is an important part of this project, but it is only our starting point. The value Librarybase brings is not from repeating what projects like OpenAlex already do, but by ''expanding'' on it, through integration with the Wikidata graph and through additions by contributors.

	~~'''~~Librarybase ~~allows expressive metadata for non-conventional publications'''. Before restricted to the world of publishing houses and academia~~, Librarybase ~~allows for~~ the ~~creation~~ of ~~document identifiers for web pages and other unconventional types of publications~~. ~~This allows them to~~ have ~~all the same metadata as you would expect~~ for ~~a book or journal article~~, ~~provided someone is available to provide it~~.		==Librarybase connects databases together==
			Much like Wikidata, Librarybase seeks to connect the various providers of publication metadata. Different industries have different standards for identifying documents, and Librarybase brings them together under its flexible data model and common ontology with Wikidata.

	~~'''~~Librarybase ~~does not replace Wikidata'''.~~ Librarybase ~~recognizes Wikidata as~~ the ~~foundation~~ of ~~its project, drawing on its rich ontology~~ for ~~describing everything about~~ publications. ~~Wikidata has a broad mission outside of this as well, and may elect~~ to ~~draw up boundaries around publication~~ metadata~~. While the Wikidata contributors decide what course to take, Librarybase offers itself~~ as ~~a place~~ for ~~experimentation beyond Wikidata's limits. Its role in the ecosystem long-term, including as~~ a ~~partial replacement for Wikidata~~, is ~~ultimately going to depend on the stability of Librarybase and the consensus of Wikidata contributors. Librarybase is otherwise not a response~~ to ~~Wikidata, but an initiative with its own goals~~.		==Librarybase allows expressive metadata for non-conventional publications==
			Before restricted to the world of publishing houses and academia, Librarybase allows for the creation of document identifiers for web pages and other unconventional types of publications. This allows them to have all the same metadata as you would expect for a book or journal article, provided someone is available to provide it.

	~~'''~~Librarybase has a ~~[[Project:Scope\|scope]] that should be interpreted broadly'''. Wikipedia is built on a foundation~~ of ~~citations~~, and ~~those citations can be~~ to ~~anything~~. ~~Anything that can feasibly be cited on Wikipedia~~, ~~from~~ a ~~tract published~~ in ~~1340~~, to a ~~politician tweet~~, ~~deserves~~ to ~~have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think~~ of ~~"publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind~~ of ~~packaged data or media, identifiable in some unique way? Assume it belongs~~. ~~We do~~ not ~~necessarily benefit from limiting our own scope. That considered, it should try~~ to ~~avoid duplicating what is on~~ Wikidata ~~as much as possible~~, ~~instead coupling~~ with ~~Wikidata through common identifiers~~.		==Librarybase does not replace Wikidata==
			Librarybase recognizes Wikidata as the foundation of its project, drawing on its rich ontology for describing everything about publications. Wikidata has a broad mission outside of this as well, and may elect to draw up boundaries around publication metadata. While the Wikidata contributors decide what course to take, Librarybase offers itself as a place for experimentation beyond Wikidata's limits. Its role in the ecosystem long-term, including as a partial replacement for Wikidata, is ultimately going to depend on the stability of Librarybase and the consensus of Wikidata contributors. Librarybase is otherwise not a response to Wikidata, but an initiative with its own goals.

	~~'''~~Librarybase ~~is built by and for the community'''. Librarybase was originally~~ [[Project:~~Operator~~\|~~incubated by Scatter~~]], a ~~private business~~, ~~but the long~~-~~term goal~~ is ~~for all aspects~~ of ~~Librarybase to~~ be ~~governed by the community that builds~~ it. ~~As the project matures and develops more long-term leaders~~, ~~responsibilities will grow~~ to ~~include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good~~, ~~rather than the hoard of any private entity~~.		==Librarybase has a [[Project:Scope\|scope]] that should be interpreted broadly==
			Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published this year. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

	~~'''~~Librarybase ~~should~~ be governed by ~~clear processes accessible to all users'''~~. As ~~a baseline,~~ the project ~~operates on the basis of consensus~~, ~~where earnest discussion leads~~ to ~~an agreed-upon outcome. This is not always~~ the ~~case~~. ~~Where there is more controversy over the outcome~~, ~~there should be clear processes for determining the community~~'s will~~. We want to ensure that each participant has~~ a ~~fair chance to participate in community processes that determine what direction~~ the ~~project takes. An inability to change the project can lead to stagnation~~.		==Librarybase is built by and for the community==
			Librarybase was originally [[Project:Operator\|incubated by a private business]], but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

	~~'''~~Librarybase should ~~use effort efficiently'''. Instead of expending~~ a ~~large amount~~ of ~~effort to complete a task~~, ~~think about how~~ to ~~accomplish~~ the ~~broader goal with less effort~~. ~~This~~ will ~~ultimately serve~~ the project in the ~~long term. And wasted effort burns out volunteers and paid staff alike~~.		==Librarybase should be governed by clear processes accessible to all users==
			As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.

	~~{{cwbn}}~~		==Librarybase should use effort efficiently==
			Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej: Harej moved page Project:Home to Project:Principles: Spinning this off as a separate page so the main page can be more functional

2023-07-11T01:46:38Z

Harej moved page Project:Home to Project:Principles: Spinning this off as a separate page so the main page can be more functional

← Older revision	Revision as of 01:46, 11 July 2023
(No difference)

Harej at 00:56, 7 June 2023

2023-06-07T00:56:21Z

← Older revision		Revision as of 00:56, 7 June 2023
Line 18:		Line 18:

	'''Librarybase should use effort efficiently'''. Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

			{{cwbn}}

Harej: links

2023-05-09T17:00:06Z

links

← Older revision		Revision as of 17:00, 9 May 2023
Line 11:		Line 11:
	'''Librarybase does not replace Wikidata'''. Librarybase recognizes Wikidata as the foundation of its project, drawing on its rich ontology for describing everything about publications. Wikidata has a broad mission outside of this as well, and may elect to draw up boundaries around publication metadata. While the Wikidata contributors decide what course to take, Librarybase offers itself as a place for experimentation beyond Wikidata's limits. Its role in the ecosystem long-term, including as a partial replacement for Wikidata, is ultimately going to depend on the stability of Librarybase and the consensus of Wikidata contributors. Librarybase is otherwise not a response to Wikidata, but an initiative with its own goals.		'''Librarybase does not replace Wikidata'''. Librarybase recognizes Wikidata as the foundation of its project, drawing on its rich ontology for describing everything about publications. Wikidata has a broad mission outside of this as well, and may elect to draw up boundaries around publication metadata. While the Wikidata contributors decide what course to take, Librarybase offers itself as a place for experimentation beyond Wikidata's limits. Its role in the ecosystem long-term, including as a partial replacement for Wikidata, is ultimately going to depend on the stability of Librarybase and the consensus of Wikidata contributors. Librarybase is otherwise not a response to Wikidata, but an initiative with its own goals.

	'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.		'''Librarybase has a [[Project:Scope\|scope]] that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

	'''Librarybase is built by and for the community'''. Librarybase was originally incubated by Scatter, a private business, but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.		'''Librarybase is built by and for the community'''. Librarybase was originally [[Project:Operator\|incubated by Scatter]], a private business, but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

	'''Librarybase should be governed by clear processes accessible to all users'''. As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.		'''Librarybase should be governed by clear processes accessible to all users'''. As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.

	'''Librarybase should use effort efficiently'''. Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej at 04:48, 8 May 2023

2023-05-08T04:48:44Z

← Older revision		Revision as of 04:48, 8 May 2023
Line 17:		Line 17:
	'''Librarybase should be governed by clear processes accessible to all users'''. As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.		'''Librarybase should be governed by clear processes accessible to all users'''. As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.

	'''Librarybase should use effort efficiently'''. Instead of ~~spending~~ a ~~lot~~ of ~~time on~~ a ~~difficult~~ task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of expending a large amount of effort to complete a task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej: another principle

2023-05-08T04:43:57Z

another principle

← Older revision		Revision as of 04:43, 8 May 2023
Line 13:		Line 13:
	'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.		'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

	'''Librarybase is built by and for the community'''. Librarybase was originally incubated by Scatter, a private business, but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it~~. A good practice around governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes~~. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.		'''Librarybase is built by and for the community'''. Librarybase was originally incubated by Scatter, a private business, but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

			'''Librarybase should be governed by clear processes accessible to all users'''. As a baseline, the project operates on the basis of consensus, where earnest discussion leads to an agreed-upon outcome. This is not always the case. Where there is more controversy over the outcome, there should be clear processes for determining the community's will. We want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. An inability to change the project can lead to stagnation.

	'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej: ce.

2023-05-08T02:22:46Z

ce.

← Older revision		Revision as of 02:22, 8 May 2023
Line 13:		Line 13:
	'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.		'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

	'''Librarybase is built by and for the community'''. ~~Though started as an initiative of~~ a private business, the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. A good practice around governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.		'''Librarybase is built by and for the community'''. Librarybase was originally incubated by Scatter, a private business, but the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. A good practice around governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

	'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej: ce.

2023-05-04T19:31:24Z

ce.

← Older revision		Revision as of 19:31, 4 May 2023
Line 13:		Line 13:
	'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.		'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

	'''Librarybase is built by and for the community'''. Though started as an initiative of a private business, the long-term goal is for Librarybase to be ~~totally~~ governed by the community that builds it. ~~Good community~~ governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. As the project matures and develops more long-term leaders, ~~the community~~ will ~~move beyond wiki governance~~ to ~~organizational governance~~. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.		'''Librarybase is built by and for the community'''. Though started as an initiative of a private business, the long-term goal is for all aspects of Librarybase to be governed by the community that builds it. A good practice around governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. As the project matures and develops more long-term leaders, responsibilities will grow to include managing the project's resources and steering its overall direction. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

	'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.		'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.

Harej: Start

2023-05-04T05:58:41Z

Start

New page

'''Librarybase''' is a project to build a database of metadata together as a community. It is inspired by projects like Wikidata and OpenAlex, but differs from both in certain respects.

'''Librarybase is a staging ground'''. Some entries are from bulk imports of middling quality. Others are efforts to assign persistent identifiers to works that otherwise never had them. This is a project that will improve incrementally. We have to start somewhere.

'''Librarybase improves on existing data'''. Librarybase does not seek to create yet another open dataset of clean academic publication metadata. While that is definitely part of it, it is just our starting point. The value Librarybase brings is not from repeating what projects like OpenAlex already do, but by ''expanding'' on it, through integration with the Wikidata graph and through additions by contributors.

'''Librarybase connects databases together'''. Much like Wikidata, Librarybase seeks to connect the various providers of publication metadata. Different industries have different standards for identifying documents, and Librarybase brings them together under its flexible data model and common ontology with Wikidata.

'''Librarybase allows expressive metadata for non-conventional publications'''. Before restricted to the world of publishing houses and academia, Librarybase allows for the creation of document identifiers for web pages and other unconventional types of publications. This allows them to have all the same metadata as you would expect for a book or journal article, provided someone is available to provide it.

'''Librarybase does not replace Wikidata'''. Librarybase recognizes Wikidata as the foundation of its project, drawing on its rich ontology for describing everything about publications. Wikidata has a broad mission outside of this as well, and may elect to draw up boundaries around publication metadata. While the Wikidata contributors decide what course to take, Librarybase offers itself as a place for experimentation beyond Wikidata's limits. Its role in the ecosystem long-term, including as a partial replacement for Wikidata, is ultimately going to depend on the stability of Librarybase and the consensus of Wikidata contributors. Librarybase is otherwise not a response to Wikidata, but an initiative with its own goals.

'''Librarybase has a scope that should be interpreted broadly'''. Wikipedia is built on a foundation of citations, and those citations can be to anything. Anything that can feasibly be cited on Wikipedia, from a tract published in 1340, to a politician tweet, deserves to have as high-quality metadata as a book published in 2012. Because this potential scope is so broad, you should think of "publication" or "document" metadata as broadly as possible. Can it be cited in a document? Could you potentially find it at a library? Is it some kind of packaged data or media, identifiable in some unique way? Assume it belongs. We do not necessarily benefit from limiting our own scope. That considered, it should try to avoid duplicating what is on Wikidata as much as possible, instead coupling with Wikidata through common identifiers.

'''Librarybase is built by and for the community'''. Though started as an initiative of a private business, the long-term goal is for Librarybase to be totally governed by the community that builds it. Good community governance is necessary because we want to ensure that each participant has a fair chance to participate in community processes that determine what direction the project takes. As the project matures and develops more long-term leaders, the community will move beyond wiki governance to organizational governance. Ultimately, Librarybase's value will come from being a public good, rather than the hoard of any private entity.

'''Librarybase should use effort efficiently'''. Instead of spending a lot of time on a difficult task, think about how to accomplish the broader goal with less effort. This will ultimately serve the project in the long term. And wasted effort burns out volunteers and paid staff alike.