Fed in Print: The Past, Present, and Future of Making Federal Reserve System Research Outputs Visible and Easily Searchable
St. Louis, Scott Richard
This presentation will focus on fedinprint.org, a web application that makes research outputs from across the United States Federal Reserve System – including twelve regional banks and the Board of Governors – searchable in one location by title, author, abstract, keyword, series, content type, bank, and Journal of Economic Learning (JEL) classification. Fed in Print also presents metadata about these research outputs to major discovery services including Google Scholar and Research Papers in Economics (RePEc). The presentation will focus on the history of Fed in Print, the System-wide cooperation required to successfully populate Fed in Print with timely, high-quality item metadata, and future plans for Fed in Print. Such future plans relate to API development, automation in content contribution, possible new RSS feeds, and keyword quality control. These future plans will necessitate an exploration on the poster of the agile software development processes used to articulate, refine, and prioritize forthcoming enhancements to Fed in Print, in balance with multiple other digital products maintained by the Research Division at the Federal Reserve Bank of St. Louis.
 Hello. Hi, Scott, how are you? I'm doing well, how are you? Doing well, thank you. Good to see you again. Over here in Germany, it's coming up to 8.30 in the evening. So I guess there in St. Louis, what are we talking about? 1.30, 2.30? 1.30 in the afternoon. 1.30 in the afternoon. Then I hope you had a good lunch. And with that, I would say, could you tell us maybe, I've had the chance to visit beautiful St. Louis in the arch many years ago. When we come to St. Louis, what's something that you would recommend to see? A touristic place, museum, a ball game, what are your highlights? Well, of course, the Gateway Arch is probably the most famous recommendation, but I recommend going to see the St. Louis Cardinals if they're in season, or taking the time to see some of the lovely museums or other attractions at Forest Park. At Forest Park, wonderful. And St. Louis Cardinals, for those that don't know American baseball, it is one of the big major league baseball teams in the city. Excellent. Okay, Scott, so just real quick, I wanted to give a brief introduction. Scott is the scholarly communication and discovery services librarian at the Federal Reserve Bank of St. Louis. His topic today for this presentation will be Fed and Print, the Past, Present, and Future of Making Federal Reserve System Research Outputs Visible and Easily Searchable. Yes, and with that, I would say you have about 15 minutes for your presentation, and then for our last round of Q&As, about five minutes. So I see the screen is shared, and with that, I'd like to give you the digital stage. Please. Thank you very much. Hello, everybody. It's great to be with all of you today at this wonderful virtual conference. As was previously stated, my name is Scott St. Louis, and I am the scholarly communication and discovery services librarian at the Federal Reserve Bank of St. Louis. My last name is just a happy coincidence. I'm not from the city of St. Louis originally, but I didn't want to let Vanity get in the way of a good job opportunity. So after library school, I jumped at the opportunity to come here. And I'm here today to share with you a quick presentation of maybe 12 minutes or so about a web application called Fed in Print. I know it can be difficult to pay attention at the very end of a rich panel, like the one that we've all enjoyed today. So I'll try to make my presentation a bit shorter than the standard 15. And before we begin, I need to inform you that I'm representing only myself with these perspectives. My thoughts don't necessarily reflect official positions of the Federal Reserve Bank of St. Louis or the Federal Reserve System. So as one colleague of mine likes to say, if you don't like my presentation, you can yell at me about it, but you can't yell at my boss about it. So let's dive in. A little bit of background about myself before the main content of the presentation. I accepted this position before finishing up library school at the University of Michigan in May of 2021. So I've been on the job for around a year now. And at the bank, I wear a lot of different hats. For example, I'm currently serving as product donor on an Agile team for Fed and Print, which as previously stated is a web application. Fed and Print indexes research outputs from throughout the Federal Reserve System and then presents metadata about those outputs to major discovery services like Google Scholar and research papers and economics, also known as REPEC, as well as the Social Science Research Network or SSRN for select banks. I also maintain the publication process for the St. Louis Fed working paper series through our internally developed research information management system. Once a year, I have a leading role in the annual citation analysis project that contributes to assessment of our economists' work. And I also process user support requests for the popular data aggregation service known as FRED. Recently, I also worked on implementation of X Libris 360 link for the benefit of our researchers. And I also provide conference planning assistance and do a number of other things, both within and beyond the traditional scope of the librarian's duties. My main goal for this presentation is really simple. I just want to provide you with a brief, high-level introduction to a resource that can be very helpful for gathering information about the research pursued by the 12 regional banks and Board of Governors that make up the Federal Reserve System. This presentation will provide you with a very brief history of Fed and Print, as well as an exploration of the Agile software development processes used to articulate, refine, and prioritize forthcoming enhancements to Fed and Print. We'll also touch very briefly on the system-wide cooperation required to successfully populate Fed and Print with timely, high-quality item metadata. And then we'll do a quick tour of key Fed and Print functionalities from the user's perspective. And finally, we'll discuss future plans for Fed and Print enhancement and improvement. So very quickly, I'll start by providing you with a history of Fed and Print as it has evolved over the past several decades. As its name suggests, Fed and Print started life in print as an index of Federal Reserve System research publications first featured as a quarterly in the Federal Reserve Bank of Philadelphia's business review. Then from 1962 to 1976, an index was released every two years with Fed and Print first appearing as a publication all its own in 1972 after receiving its present day title two years earlier. The scope of Fed and Print expanded in the 1980s to include most textual publications from the various research departments scattered throughout the Federal Reserve System. And then by 2000, publication of the paper copy had ceased with successful online availability of the index. Expansion of scope occurred again in 2002 to include select publications from Federal Reserve departments other than research departments and streamlined submission of Fed and Print content to research papers and economics. The REPEC database took place in the 2010s. And today you can read more about the history of Fed and Print in more detail at fedandprint.org slash about. Changing gears now, I want to provide you with a quick look at the agile software development practices used to document, refine, prioritize, and implement feature enhancements, bug fixes, and other improvements to Fed and Print. Fed and Print is one product line on an agile team, including multiple products, and therefore multiple product owners. So in the course of my time at the Federal Reserve Bank of St. Louis thus far, we have used a mixture of scrum and Kanban methodologies within the agile development universe to strike a balance between the multiplicity of needs that our product owners bring to the table and the developer capacity we have on hand to address those needs. We strive to articulate product needs through the voice of the user by compiling backlogs of user stories that explain the business value of various enhancements and fixes specifically from the user's perspective so that this perspective remains top of mind throughout the development process. And those stories are then submitted to what are called refinement sessions in which multiple product owners and developers come together to improve how the user stories are written for greater instructiveness and comprehensibility from the developer perspective. Refinement meetings are also where our amazing developers estimate the relative complexity of various stories through a pointing system. Prioritization meetings then take place in order to sort out the relative importance and urgency of various user stories among the several products for an upcoming two-week sprint. And within those two-week sprints, peer accountability for implementation of enhancements and fixes guided by those user stories takes place in the form of daily stand-ups in which developers and product owners alike report to one another on what progress they've made the previous day, what progress they plan to make in the day ahead, as well as any blockers to productivity that they are experiencing. Near the end of each two-week sprint, review meetings take place in which multiple development teams come together to report and demonstrate their two weeks' worth of progress to one another. And retrospectives or retros also take place in which the product owners and developers comprising an individual team come together to reflect on what went well and what could have gone better in the previous two-week sprint. A quick look at the sheer amount of resources available on Fed and Print might leave you wondering how the index gets updated in a timely fashion with new publications coming out more or less every day throughout the system. And the answer is that that responsibility is collective in nature. It falls to designated content contributors at all 12 regional banks within the Federal Reserve System, as well as the Board of Governors of the Federal Reserve. For example, I serve as the content contributor for the Federal Reserve Bank of St. Louis. Content contributors are responsible for adding new series level, item level, and author-level metadata to Fed and Print as necessary to ensure that the index remains up to date. On a quarterly basis, as overall system maintainer for Fed and Print, I also assemble the content contributors throughout the system to share progress updates and listen for potential future needs that will need to tackle collaboratively. One example of recent collaborative work in which content contributors have participated together is some basic keyword quality control for Fed and Print. This is definitely still a work in progress, but as I'll talk about again later, we're hoping to remove typos and consolidate duplicative keywords that have emerged in Fed and Print over the years. So now let's turn to the meat and potatoes of the presentation. We'll take a quick tour of Fed and Print from the user's perspective. I hope that this quick overview will be of interest to you and that you'll keep Fed and Print in mind for yourself and your patrons as a useful point of discovery for a rich variety of resources from the Federal Reserve System. Turning now to the home page at fedandprint.org, you'll see that there are multiple ways to access the latest items added to Fed and Print. The home page itself displays a few of these items. You can also visit those recent items by visiting the individual websites of the 12 regional banks, as well as the Board of Governors, down at the bottom of the page. Longer lists of most recent items for the system as a whole, as well as for individual banks, and the Board are available via the latest tab up at the top of the home page, as you can see here. We also make RSS feeds of latest items available by bank, as well as by a couple of keywords at present. Those keywords are COVID-19 and diversity. For those users interested in browsing for content of interest rather than searching, we make browse functionality available by bank, publication series, publication type, author, Journal of Economic Literature classification, and keyword. So there are many different ways to slice up the content for your particular research needs. For example, Browse by Series will take you to a page displaying all of the publication series available in Fed and Print, organized by bank or Board of Governors. We also make it possible to see which Federal Reserve System publications have been assigned Journal of Economic Literature classifications. For those users interested in a more traditional search experience, you can enter search terms and see what comes up for title, author, abstract, keywords, or all of the above. And once a user has been served with search results, a number of filtering options remain available to make it possible for more refined searches to proceed. Fed and Print also offers Boolean search capability, as well as the ability to sort by relevance, ascending date, descending date, or alphabetical order. Turning now to future plans for the Fed and Print application, an API is currently under development that will enable public users to access series level, item level, and author level data programmatically using tools like Python, for example. The API will also empower our administrative users, also known as our content contributors, to automate records creation for Fed and Print. And as previously stated, our keyword quality control work is ongoing as well. In addition to the manual review that content contributors jointly pursued, I wrote a Python program utilizing web scraping and fuzzy string matching to identify duplicative keywords as good candidates for consolidation. And additionally, I'll be working with our developers in the not so distant future to add dictionary and spell check functionalities to our content contribution admin forms as a way of cutting down a bit on the long-term sprawl of keywords that we've noticed previously. And that's all for me today. I hope you've enjoyed the presentation and will keep Fed and Print in mind for your patron support and research needs, even after the conference adjourns. Please feel free to connect with us at the St. Louis Fed in any of the ways listed here. Please also consider joining us in November for the 2022 Beyond the Numbers conference. Our call for proposals is available at the link provided on this slide with a deadline of June 30. And you can also contact me via email at the address provided at the top of the slide. That's scott.saintluis.shtls.frb.org. Thank you very much to all of you for attending and to the conference organizers for such a wonderful, seamless experience. Thanks very much. And thank you, Scott, Richard St. Louis. And name that I cannot forget. Fantastic. Good. We are coming up to our final Q&A session here. And I'm just going to jump right into it. And the first question we have here is, let me see here, are your user stories available for interested colleagues? That's a good question. I'd have to follow up with folks on the team to see if that's possible. But I can't provide an answer one way or another right now. If however, the person who sent that question would like to send a note my way to that email address, we can talk more about the way that the agile development processes work for Fed and Print. Super. OK, thank you. Good. Then the next question we have, do you know about how many papers are added to Fed and Print each year? And how many staff there are to manage the system? Is it just yourself doing this? No, it's not just me doing it. We have content contributors at all 12 regional banks, as well as the Board of Governors of the Federal Reserve System. So those are folks just responsible for content contribution. I serve as the overall system maintainer, coordinating activity from those different content contributors. But I also work with three wonderful developers here at the St. Louis Fed, who make all of this technologically possible in collaboration with what I'm hearing from our stakeholders. Super, thank you. Let me see if we have another question coming in. Yes, the next one we have here. I like the idea to offer RSS feeds for current topics. Do you have any feedback from users, usage numbers? Not off the top of my head, no. But I think we're hoping to add possible additional RSS feeds in the future. So stay tuned. Very good. Good. Our next question. On your website, you differentiate between journal article, conference paper, and speech. Who provides the metadata for this? The Fed? Yes, that would be correct. The metadata is provided by our system content contributors using an admin form. And hopefully in the future, we'll be able to automate some of that using the API that's currently under development. It's an interesting kind of byproduct of the scholarly communication workflows in the economics field specifically. I found in discussion with colleagues that the economics field has a lot of open practices, but not necessarily a lot of open language. So of course, economists very often circulate working papers before publishing their findings and peer reviewed articles. And working papers have sort of a publication life of their own before the corresponding journal article that is published following input feedback from colleagues. So we make working papers available. And we update versioning as we go along on the St. Louis Fed Working Papers website, for instance. And then we make available in Fed and print information about when a working paper has been published as a peer reviewed journal article. OK, very good. Excellent. Yeah. And our final question, can anyone get slash use your metadata and in any way? Let's see. So I think that the metadata will be accessible through the API once that project is released at some point within the next few weeks or months. It just depends on how long it takes us to finish up the last batch of user stories that our developers are working through right now. And then I think we'll have to talk with folks about terms of use for metadata to make sure that the information we make available is used in appropriate ways. But there should be certain parameters in place to make sure that public information is available for public consumption in ways that our users see necessary or fit. That's it. Thank you. Yeah. And once again, Scott, thank you for your presentation and also for taking some time to answer our Q&A sessions. And I'd like to give you a virtual applause, hopefully from all of our participants around the world. Some of them may be speaking not Asia, but in the US, it's a good time. Great. Thank you very much. Yeah. Thank you. Yeah.
 Hello.  Hi, Scott, how are you?  I'm doing well, how are you?  Doing well, thank you. Good to see you again.  Over here in Germany, it's coming up to 8.30 in the evening.  So I guess there in St. Louis, what are we talking about?  1.30, 2.30?  1.30 in the afternoon.  1.30 in the afternoon.  Then I hope you had a good lunch.  And with that, I would say, could you tell us maybe,  I've had the chance to visit beautiful St. Louis  in the arch many years ago.  When we come to St. Louis,  what's something that you would recommend to see?  A touristic place, museum, a ball game,  what are your highlights?  Well, of course, the Gateway Arch is probably  the most famous recommendation,  but I recommend going to see the St. Louis Cardinals  if they're in season, or taking the time  to see some of the lovely museums  or other attractions at Forest Park.  At Forest Park, wonderful.  And St. Louis Cardinals,  for those that don't know American baseball,  it is one of the big major league baseball teams in the city.  Excellent.  Okay, Scott, so just real quick,  I wanted to give a brief introduction.  Scott is the scholarly communication  and discovery services librarian  at the Federal Reserve Bank of St. Louis.  His topic today for this presentation will be Fed and Print,  the Past, Present, and Future  of Making Federal Reserve System Research Outputs Visible  and Easily Searchable.  Yes, and with that, I would say you have about 15 minutes  for your presentation,  and then for our last round of Q&As, about five minutes.  So I see the screen is shared,  and with that, I'd like to give you the digital stage.  Please.  Thank you very much.  Hello, everybody.  It's great to be with all of you today  at this wonderful virtual conference.  As was previously stated, my name is Scott St. Louis,  and I am the scholarly communication  and discovery services librarian  at the Federal Reserve Bank of St. Louis.  My last name is just a happy coincidence.  I'm not from the city of St. Louis originally,  but I didn't want to let Vanity get in the way  of a good job opportunity.  So after library school,  I jumped at the opportunity to come here.  And I'm here today to share with you a quick presentation  of maybe 12 minutes or so  about a web application called Fed in Print.  I know it can be difficult to pay attention  at the very end of a rich panel,  like the one that we've all enjoyed today.  So I'll try to make my presentation  a bit shorter than the standard 15.  And before we begin, I need to inform you  that I'm representing only myself with these perspectives.  My thoughts don't necessarily reflect official positions  of the Federal Reserve Bank of St. Louis  or the Federal Reserve System.  So as one colleague of mine likes to say,  if you don't like my presentation,  you can yell at me about it,  but you can't yell at my boss about it.  So let's dive in.  A little bit of background about myself  before the main content of the presentation.  I accepted this position before finishing up library school  at the University of Michigan in May of 2021.  So I've been on the job for around a year now.  And at the bank, I wear a lot of different hats.  For example, I'm currently serving as product donor  on an Agile team for Fed and Print,  which as previously stated is a web application.  Fed and Print indexes research outputs  from throughout the Federal Reserve System  and then presents metadata about those outputs  to major discovery services like Google Scholar  and research papers and economics, also known as REPEC,  as well as the Social Science Research Network  or SSRN for select banks.  I also maintain the publication process  for the St. Louis Fed working paper series  through our internally developed  research information management system.  Once a year, I have a leading role  in the annual citation analysis project  that contributes to assessment of our economists' work.  And I also process user support requests  for the popular data aggregation service known as FRED.  Recently, I also worked on implementation  of X Libris 360 link for the benefit of our researchers.  And I also provide conference planning assistance  and do a number of other things, both within  and beyond the traditional scope of the librarian's duties.  My main goal for this presentation is really simple.  I just want to provide you with a brief,  high-level introduction to a resource  that can be very helpful for gathering information  about the research pursued by the 12 regional banks  and Board of Governors that make up  the Federal Reserve System.  This presentation will provide you with a very brief history  of Fed and Print, as well as an exploration  of the Agile software development processes  used to articulate, refine, and prioritize  forthcoming enhancements to Fed and Print.  We'll also touch very briefly on the system-wide cooperation  required to successfully populate Fed and Print  with timely, high-quality item metadata.  And then we'll do a quick tour of key Fed and Print  functionalities from the user's perspective.  And finally, we'll discuss future plans  for Fed and Print enhancement and improvement.  So very quickly, I'll start by providing you  with a history of Fed and Print as it has evolved  over the past several decades.  As its name suggests, Fed and Print started life in print  as an index of Federal Reserve System research publications  first featured as a quarterly in the Federal Reserve Bank  of Philadelphia's business review.  Then from 1962 to 1976, an index was released  every two years with Fed and Print first appearing  as a publication all its own in 1972  after receiving its present day title two years earlier.  The scope of Fed and Print expanded in the 1980s  to include most textual publications  from the various research departments scattered  throughout the Federal Reserve System.  And then by 2000, publication of the paper copy  had ceased with successful online availability of the index.  Expansion of scope occurred again in 2002  to include select publications from Federal Reserve departments  other than research departments  and streamlined submission of Fed and Print content  to research papers and economics.  The REPEC database took place in the 2010s.  And today you can read more about the history of Fed and Print  in more detail at fedandprint.org slash about.  Changing gears now, I want to provide you with a quick look  at the agile software development practices used  to document, refine, prioritize,  and implement feature enhancements, bug fixes,  and other improvements to Fed and Print.  Fed and Print is one product line on an agile team,  including multiple products,  and therefore multiple product owners.  So in the course of my time at the Federal Reserve Bank  of St. Louis thus far, we have used a mixture of scrum  and Kanban methodologies within the agile development universe  to strike a balance between the multiplicity of needs  that our product owners bring to the table  and the developer capacity we have on hand  to address those needs.  We strive to articulate product needs  through the voice of the user by compiling backlogs  of user stories that explain the business value  of various enhancements and fixes specifically  from the user's perspective  so that this perspective remains top of mind  throughout the development process.  And those stories are then submitted  to what are called refinement sessions  in which multiple product owners and developers come together  to improve how the user stories are written  for greater instructiveness and comprehensibility  from the developer perspective.  Refinement meetings are also where our amazing developers  estimate the relative complexity of various stories  through a pointing system.  Prioritization meetings then take place  in order to sort out the relative importance  and urgency of various user stories  among the several products for an upcoming two-week sprint.  And within those two-week sprints,  peer accountability for implementation of enhancements  and fixes guided by those user stories  takes place in the form of daily stand-ups  in which developers and product owners alike  report to one another on what progress they've made  the previous day, what progress they plan to make  in the day ahead, as well as any blockers to productivity  that they are experiencing.  Near the end of each two-week sprint,  review meetings take place in which  multiple development teams come together to report  and demonstrate their two weeks' worth of progress  to one another.  And retrospectives or retros also take place  in which the product owners and developers  comprising an individual team come together  to reflect on what went well  and what could have gone better  in the previous two-week sprint.  A quick look at the sheer amount of resources  available on Fed and Print  might leave you wondering how the index  gets updated in a timely fashion  with new publications coming out more or less  every day throughout the system.  And the answer is that that responsibility  is collective in nature.  It falls to designated content contributors  at all 12 regional banks within the Federal Reserve System,  as well as the Board of Governors of the Federal Reserve.  For example, I serve as the content contributor  for the Federal Reserve Bank of St. Louis.  Content contributors are responsible  for adding new series level, item level,  and author-level metadata to Fed and Print  as necessary to ensure that the index remains up to date.  On a quarterly basis, as overall system  maintainer for Fed and Print, I also  assemble the content contributors throughout the system  to share progress updates and listen for potential future needs  that will need to tackle collaboratively.  One example of recent collaborative work  in which content contributors have participated together  is some basic keyword quality control for Fed and Print.  This is definitely still a work in progress,  but as I'll talk about again later,  we're hoping to remove typos and consolidate duplicative keywords  that have emerged in Fed and Print over the years.  So now let's turn to the meat and potatoes of the presentation.  We'll take a quick tour of Fed and Print  from the user's perspective.  I hope that this quick overview will be of interest to you  and that you'll keep Fed and Print in mind for yourself  and your patrons as a useful point of discovery  for a rich variety of resources from the Federal Reserve  System.  Turning now to the home page at fedandprint.org,  you'll see that there are multiple ways  to access the latest items added to Fed and Print.  The home page itself displays a few of these items.  You can also visit those recent items  by visiting the individual websites of the 12 regional banks,  as well as the Board of Governors,  down at the bottom of the page.  Longer lists of most recent items for the system  as a whole, as well as for individual banks,  and the Board are available via the latest tab up  at the top of the home page, as you can see here.  We also make RSS feeds of latest items available by bank,  as well as by a couple of keywords at present.  Those keywords are COVID-19 and diversity.  For those users interested in browsing for content of interest  rather than searching, we make browse functionality  available by bank, publication series, publication type,  author, Journal of Economic Literature classification,  and keyword.  So there are many different ways to slice up  the content for your particular research needs.  For example, Browse by Series will take you to a page  displaying all of the publication series  available in Fed and Print, organized by bank  or Board of Governors.  We also make it possible to see which Federal Reserve System  publications have been assigned Journal of Economic Literature  classifications.  For those users interested in a more traditional search  experience, you can enter search terms  and see what comes up for title, author, abstract, keywords,  or all of the above.  And once a user has been served with search results,  a number of filtering options remain available to make it  possible for more refined searches to proceed.  Fed and Print also offers Boolean search capability,  as well as the ability to sort by relevance, ascending date,  descending date, or alphabetical order.  Turning now to future plans for the Fed and Print application,  an API is currently under development  that will enable public users to access  series level, item level, and author level data  programmatically using tools like Python, for example.  The API will also empower our administrative users,  also known as our content contributors,  to automate records creation for Fed and Print.  And as previously stated, our keyword quality control  work is ongoing as well.  In addition to the manual review that content contributors  jointly pursued, I wrote a Python program utilizing  web scraping and fuzzy string matching  to identify duplicative keywords as good candidates  for consolidation.  And additionally, I'll be working with our developers  in the not so distant future to add dictionary and spell  check functionalities to our content contribution admin  forms as a way of cutting down a bit on the long-term sprawl  of keywords that we've noticed previously.  And that's all for me today.  I hope you've enjoyed the presentation  and will keep Fed and Print in mind for your patron support  and research needs, even after the conference adjourns.  Please feel free to connect with us at the St. Louis Fed  in any of the ways listed here.  Please also consider joining us in November for the 2022  Beyond the Numbers conference.  Our call for proposals is available at the link provided  on this slide with a deadline of June 30.  And you can also contact me via email at the address provided  at the top of the slide.  That's scott.saintluis.shtls.frb.org.  Thank you very much to all of you for attending  and to the conference organizers for such a wonderful,  seamless experience.  Thanks very much.  And thank you, Scott, Richard St. Louis.  And name that I cannot forget.  Fantastic.  Good.  We are coming up to our final Q&A session here.  And I'm just going to jump right into it.  And the first question we have here is, let me see here,  are your user stories available for interested colleagues?  That's a good question.  I'd have to follow up with folks on the team  to see if that's possible.  But I can't provide an answer one way or another right now.  If however, the person who sent that question  would like to send a note my way to that email address,  we can talk more about the way that the agile development  processes work for Fed and Print.  Super.  OK, thank you.  Good.  Then the next question we have, do you  know about how many papers are added to Fed and Print each year?  And how many staff there are to manage the system?  Is it just yourself doing this?  No, it's not just me doing it.  We have content contributors at all 12 regional banks,  as well as the Board of Governors of the Federal Reserve  System.  So those are folks just responsible for content  contribution.  I serve as the overall system maintainer,  coordinating activity from those different content  contributors.  But I also work with three wonderful developers  here at the St. Louis Fed, who make all of this technologically  possible in collaboration with what I'm  hearing from our stakeholders.  Super, thank you.  Let me see if we have another question coming in.  Yes, the next one we have here.  I like the idea to offer RSS feeds for current topics.  Do you have any feedback from users, usage numbers?  Not off the top of my head, no.  But I think we're hoping to add possible additional RSS feeds  in the future.  So stay tuned.  Very good.  Good.  Our next question.  On your website, you differentiate  between journal article, conference paper, and speech.  Who provides the metadata for this?  The Fed?  Yes, that would be correct.  The metadata is provided by our system content contributors  using an admin form.  And hopefully in the future, we'll  be able to automate some of that using the API that's  currently under development.  It's an interesting kind of byproduct  of the scholarly communication workflows  in the economics field specifically.  I found in discussion with colleagues  that the economics field has a lot of open practices,  but not necessarily a lot of open language.  So of course, economists very often  circulate working papers before publishing their findings  and peer reviewed articles.  And working papers have sort of a publication life  of their own before the corresponding journal  article that is published following input feedback  from colleagues.  So we make working papers available.  And we update versioning as we go along  on the St. Louis Fed Working Papers website, for instance.  And then we make available in Fed and print information  about when a working paper has been published as a peer  reviewed journal article.  OK, very good.  Excellent.  Yeah.  And our final question, can anyone  get slash use your metadata and in any way?  Let's see.  So I think that the metadata will  be accessible through the API once that project is released  at some point within the next few weeks or months.  It just depends on how long it takes us  to finish up the last batch of user stories that our developers  are working through right now.  And then I think we'll have to talk with folks  about terms of use for metadata to make  sure that the information we make available  is used in appropriate ways.  But there should be certain parameters in place  to make sure that public information is  available for public consumption in ways that our users see  necessary or fit.  That's it.  Thank you.  Yeah.  And once again, Scott, thank you for your presentation  and also for taking some time to answer our Q&A sessions.  And I'd like to give you a virtual applause, hopefully  from all of our participants around the world.  Some of them may be speaking not Asia,  but in the US, it's a good time.  Great.  Thank you very much.  Yeah.  Thank you.  Yeah.
16_Scott_Richard_St_0_1199.png 16_Scott_Richard_St_1200_1703.png 16_Scott_Richard_St_1704_2159.png 16_Scott_Richard_St_2160_3347.png 16_Scott_Richard_St_3348_3899.png 16_Scott_Richard_St_3900_9239.png 16_Scott_Richard_St_9240_12779.png 16_Scott_Richard_St_12780_14639.png 16_Scott_Richard_St_14640_15215.png 16_Scott_Richard_St_15216_15767.png 16_Scott_Richard_St_15768_16091.png 16_Scott_Richard_St_16092_16355.png 16_Scott_Richard_St_16356_16883.png 16_Scott_Richard_St_16884_17399.png 16_Scott_Richard_St_17400_17675.png 16_Scott_Richard_St_17676_18179.png 16_Scott_Richard_St_18180_19667.png 16_Scott_Richard_St_19668_19979.png 16_Scott_Richard_St_19980_20291.png 16_Scott_Richard_St_20292_20843.png 16_Scott_Richard_St_20844_21467.png 16_Scott_Richard_St_21468_22295.png 16_Scott_Richard_St_22296_23207.png 16_Scott_Richard_St_23208_23615.png 16_Scott_Richard_St_23616_25607.png 16_Scott_Richard_St_25608_25703.png 16_Scott_Richard_St_25704_26063.png 16_Scott_Richard_St_26064_27085.png