The Future of Publishing

BISG’s Rights Committee launches a new rights taxonomy

BISG’s Rights Committee launches a new rights taxonomy

About the Author

Brian O'Leary is Executive Director of BISG. Maya Fakundiny serves as Operations Manager of BISG.

BISG maintains five standing committees: metadata, rights, subject codes, supply chain, and workflow. They meet monthly, working to solve problems that affect two or more parts of the industry. While some of the problems they address are immediate and pressing, many are “horizon” issues that block industry growth or limit opportunities to try new approaches.

The work underway in BISG’s Rights Committee is a bit of both. Surveys and anecdotal information have consistently told us that rights functions need both better technology and a path forward to handle a growing demand for both inbound and outbound rights and permissions. Reporting is also a burden for many rightsholders.

To address these challenges, a working group within the committee has developed a taxonomy for the exchange of rights information. This taxonomy defines a minimum viable dataset for the communication of rights requests and rights transaction data. The taxonomy helps streamline and potentially automate two potential parts of the rights supply chain:

The proposed taxonomy was described at a very successful BISG event that took place last week in New York. An audience of publishers, literary agents, rights managers, and technology providers heard how the new taxonomy could streamline work and make reporting both transparent and easier to manage.

Over the past three decades, BISG has made other attempts to improve rights management. These efforts included development of the first “standard” form for reporting rights and royalties, an influential attempt that gained some acceptance in the 1990s. Earlier this decade, the rights committee developed a new taxonomy that struggled to gain adoption in the broader marketplace.

Two aspects of this most recent effort offer promise for the industry. The working group focused on developing standards that would help “machines talk to other machines,” creating definitions that could be mapped across systems. It also started with the assumption that the prevailing metadata standard, ONIX for Books, could be used or enhanced to provide the supply chain with a single way to convey the critical information required in the taxonomy.

To continue reading the article, please fill the below form

    Disclaimer: This is to inform readers that the views, thoughts, and opinions expressed in the article belong solely to the author, and do not reflect the views of Amnet.

    Copyright © 2022 Amnet. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other non-commercial uses permitted by copyright law.

    Amnet
https://amnet-systems.com/thought-leadership/the-future-of-publishing-articles/bisgs-rights-committee-launches-a-new-rights-taxonomy/
amnet-systems.com
CC-MAIN-2024-22
228513
application/http; msgtype=response
sha1:2YNB6R7EPUG7TEVYSJJ4BZW4WQOG5K43
<urn:uuid:a3d999ef-3515-4eca-8af3-d8124862b3f9>
2024-05-28T16:18:38Z
172.67.70.69
text/html
sha1:FBAAHEXCJFVCOSTW5KPT2L3KUS3OO7PY
<urn:uuid:7d61a51f-9292-4d8f-a205-34ecc57e5499>
https://amnet-systems.com/thought-leadership/the-future-of-publishing-articles/bisgs-rights-committee-launches-a-new-rights-taxonomy/
response
<urn:uuid:81a369e9-1d73-4fe9-84cc-ac59a3d36cda>
isPartOf: CC-MAIN-2024-22
publisher: Common Crawl
description: Wide crawl of the web for May 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-204
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/