{"id":720,"date":"2020-10-02T20:22:25","date_gmt":"2020-10-02T20:22:25","guid":{"rendered":"https:\/\/software.sil.org\/audioprojectmanager\/?page_id=720"},"modified":"2026-06-25T17:12:25","modified_gmt":"2026-06-25T17:12:25","slug":"project-setup","status":"publish","type":"page","link":"https:\/\/software.sil.org\/audioprojectmanager\/learn-apm\/project-setup\/","title":{"rendered":"Project Setup"},"content":{"rendered":"<p>The basic project setup consists of two steps:<\/p>\n<ol>\n<li>Define the name, type, language and tags.<\/li>\n<li>Describe the Sections and Passages.<\/li>\n<\/ol>\n<h2>Define the type, language and tags<\/h2>\n<p>Audio Project Manager has two types: <code>Scripture projects<\/code> and <code>General projects<\/code>. Scripture projects sync with <a href=\"https:\/\/software.sil.org\/audioprojectmanager\/resources\/\">Paratext<\/a> (both pushing to and pulling from) and General do not. Scripture projects allow vernacular transcriptions to be synced or back translations: either phrase oriented or whole passage retellings. Scripture projects have a book name as part of the reference and General projects do not. Scripture projects are frequently named for the book of which they are transcriptions. General projects have no real convention concerning their names.<\/p>\n<p>The language specifies the language of the content. Tags are used to describe if the project is just for testing or if it is a back translation project. You are free to add other tags that are useful to you and these tags will appear on the project cards.<\/p>\n<h2>Describe the Sections and Passages<\/h2>\n<p>The project advanced settings allows you to call the Sections by other names if the word Sections isn&#8217;t particularly helpful in describing the content you will be transcribing. The &#8216;Section&#8217; represents the work assigned to a team member in a team project. (Sometimes it is helpful if multiple audio files that are related are assigned to the same person so that work is consistent for aa particular &#8216;section&#8217;.)<\/p>\n<p>There are two methods for adding the &#8216;plan&#8217; describing the sections and passages. You can either use <code>Audio Project Manager<\/code> to create them using the add buttons or you can create a spreadsheet in Excel and copy and paste it into Audio Project Manager. Some projects have a spreadsheet they are using for their project description in Excel so this sheet can be &#8220;shared&#8221; with <code>Audio Project Manager<\/code> to describe the project in the same way. A much more detailed description of how to setup Sections and passages is described in the Help file [<a href=\"http:\/\/help.audioprojectmanager.org\/en\/index.htm#t=Setup_procedures%2FSet-up-procedures_overview.htm\" target=\"_blank\" rel=\"noopener\">here<\/a>].<\/p>\n<p>Here is a video of <a href=\"https:\/\/youtu.be\/L1c9mB4JrFk\" target=\"_blank\" rel=\"noopener noreferrer\">setting up a project<\/a>.<\/p>\n<h1>Project Setup and Resources for Oral Bible Translation (OBT)<\/h1>\n<p>\n  When setting up a new Oral Bible Translation (OBT) project in Audio Project<br \/>\n  Manager (APM), configuring your project scope, pericopes, and reference audio<br \/>\n  resources efficiently is key. Below is updated information on recent feature<br \/>\n  developments, automated workflows, and guidelines for managing project<br \/>\n  content.\n<\/p>\n<h2>1. Defining Project Structure and Pericopes<\/h2>\n<p>\n  Q: How do I get standard pericope breakdowns for each book of the Bible when<br \/>\n  setting up an APM project?\n<\/p>\n<p>\nThe current version supports creation of all the sections and passages using a spreadsheet but these have to be hand edited. Samples are available for Luke and Genesis and others may be available from friends or partner organizations.\n<\/p>\n<p>\n  In upcoming versions of APM, the project creation process has been<br \/>\n  significantly streamlined. If you have a USFM (Unified Standard Format<br \/>\n  Markers) file for a specific book of the Bible, APM can automatically generate<br \/>\n  the pericopes for you:\n<\/p>\n<ul>\n<li>\n    Section Headers:&nbsp;APM extracts these directly from the USFM file to<br \/>\n    define major divisions.\n  <\/li>\n<li>\n    Passages:&nbsp;Each text paragraph within the file automatically becomes a<br \/>\n    designated passage.\n  <\/li>\n<\/ul>\n<p>\n  Source Material:&nbsp;Any Bible content available in the Digital Bible Library<br \/>\n  (DBL) can be utilized as your structural model for this process.\n<\/p>\n<h2>2. Procuring and Integrating Reference Audio<\/h2>\n<p>\n  Q: Are teams responsible for managing copyright permissions and accessing<br \/>\n  reference audio, or can APM assist?\n<\/p>\n<p>\n  APM provides integrated options to pull legitimate reference resources<br \/>\n  automatically, reducing the copyright burden on local teams.\n<\/p>\n<h3 id=\"h.7erz3in4u9sv\">Automated Resource Options<\/h3>\n<ul>\n<li>\n    Bible Brain Integration:&nbsp;Through the Internalize&nbsp;step, users can<br \/>\n    pull audio content directly from Bible Brain.\n  <\/li>\n<\/ul>\n<ul>\n<li>\n    You can choose whether to apply this content at the section&nbsp;or<br \/>\n    passage&nbsp;level.\n  <\/li>\n<li>The tool supports syncing audio up to the full book&nbsp;level.<\/li>\n<li>\n    Note: Bible Brain content is generally pre-approved as a resource for OBT<br \/>\n    work.\n  <\/li>\n<\/ul>\n<ul>\n<li>\n    Aquifer &amp; FaithBridge (AI Summaries):&nbsp;You can utilize FaithBridge<br \/>\n    to summarize scriptural content available in the Aquifer database using AI.<br \/>\n    This generates non-scripture audio resources that teams can leverage during<br \/>\n    internalization.\n  <\/li>\n<\/ul>\n<h3 id=\"h.9uy0uubkr5bq\">Alternative &amp; Manual Resource Options<\/h3>\n<p>\n  If teams wish to use reference audio outside of Bible Brain or Aquifer, they<br \/>\n  must manage access independently:\n<\/p>\n<ul>\n<li>\n    Paratext Licenses \/ Logos:&nbsp;Teams can use content they have unlocked via<br \/>\n    a Paratext license or commercial software like Logos, though this content is<br \/>\n    not natively integrated for auto-syncing within APM.\n  <\/li>\n<li>\n    Custom Negotiations:&nbsp;Teams are free to negotiate permissions for<br \/>\n    external audio resources directly with copyright holders.\n  <\/li>\n<\/ul>\n<h2>3. Uploading Reference Audio: Automated vs. Manual<\/h2>\n<p>\n  Q: Once reference audio is obtained, do we have to manually slice and upload<br \/>\n  it to the Internalization step, or can it be automatically matched?\n<\/p>\n<ul>\n<li>\n    For Integrated Resources (Bible Brain &amp; Aquifer):&nbsp;The process is<br \/>\n    completely automated. If you use Bible Brain or Aquifer\/FaithBridge<br \/>\n    summaries, APM automatically matches, segments, and includes the audio in<br \/>\n    the correct internalization steps.\n  <\/li>\n<li>\n    For External\/Custom Resources:&nbsp;If you are using external audio files<br \/>\n    not sourced from Bible Brain or Aquifer, you will still need to manually<br \/>\n    slice the audio to match your pericope\/passage lengths and upload them to<br \/>\n    the project manually.\n  <\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The basic project setup consists of two steps: Define the name, type, language and tags. Describe the Sections and Passages. Define the type, language and tags Audio Project Manager has two types: Scripture projects and General projects. Scripture projects sync with Paratext (both pushing to and pulling from) and General do not. Scripture projects allow [&hellip;]<\/p>\n","protected":false},"author":42,"featured_media":0,"parent":26,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"hide_sidebar":false,"hide_h1":false,"footnotes":""},"class_list":["post-720","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/pages\/720","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/comments?post=720"}],"version-history":[{"count":14,"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/pages\/720\/revisions"}],"predecessor-version":[{"id":739,"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/pages\/720\/revisions\/739"}],"up":[{"embeddable":true,"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/pages\/26"}],"wp:attachment":[{"href":"https:\/\/software.sil.org\/audioprojectmanager\/wp-json\/wp\/v2\/media?parent=720"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}