Even if the granular details are tracked in GitHub, JIRA is useful for communicating with the project about what work is being done. You might think about what issues one might open in JIRA for the purpose of letting the community know this work is being done, placing it in the context of other development.

-Tod

On Feb 16, 2021, at 8:52 AM, Ian Walls <ian@bywatersolutions.com> wrote:

The main reason I'm eschewing JIRA for this module is that it's highly customized around the FOLIO Project's development approach, which involves Epics/Stories/Features/etc, POs and institutional rankings.  This is a lot of overhead, and all-in-all unnecessary for this module.  I'm aiming for a simpler approach, wherein any person who finds an issue, has a feature idea or needs to ask a question can just go to one place online, enter what they need to communicate, and submit.  This seems to be me to be more 'right-sized' for this particular endeavour.


Ian

On Mon, Feb 15, 2021 at 9:22 AM Ann-Marie Breaux <abreaux@ebsco.com> wrote:

Hi Ian,

 

Just one comment – you can still use Jira for tracking work even if the work is not managed by the PC and SIGs. If it’s easier for you to do it in Github, that’s fine. And for this audience, I’m guessing folks are pretty comfortable with Github already. For the larger FOLIO user community, they are more comfortable and familiar with Jira rather than Github.

 

Thanks,

A-M

 

Ann-Marie Breaux

Vice President, Workflow Management Services

EBSCO Information Services

10 Estes Street

Ipswich, MA  01938

abreaux@ebsco.com

Mobile: +1-678-427-4875

 

From: data-migration@ole-lists.openlibraryfoundation.org <data-migration@ole-lists.openlibraryfoundation.org> On Behalf Of Ian Walls
Sent: Monday, February 15, 2021 8:44 AM
To: data-migration@ole-lists.openlibraryfoundation.org
Cc: Dennis Bridges <dbridges@ebsco.com>; marcia1 folio <marcia1.folio@gmail.com>
Subject: Re: FOLIO Data Migration Data Migration meeting on Monday, Feb 15, at 11 EST

 

CAUTION: External E-mail

 

Data Migration folks,

 

 

Alas, I will not be able to attend today's meeting, due to the US holiday.  But, I'll attempt to answer some of the possible questions/concerns in advance:

  • My plan is to look at using PostgresT to provide a RESTful API to the FOLIO database for a tenant.  This will require some configuration to be able to handle the multi-schema approach that FOLIO takes for per-module tables, but there are methods available for this.  One limitation, though, will be that it will not be possible to do cross-schema queries... this is thankfully outside the school of bulk upsert APIs
  • This module would be maintained by me, and anyone else who would be willing to contribute time and effort.  It would not be a part of the FOLIO Project, as directed by the Product Council, as we've found that bulk data import is just not a high priority for the project at this time.  I feel that the bureaucratic overhead of trying to weave this module into the rest of the Project's priorities would bog down the development timeline significantly.
  • As such, bugs and issues for this module would be reported/managed using GitHub Issues, rather than JIRA.
  • The general intent would be for this module to be used during migration time, rather than being a permanent part of a FOLIO tenant, but it's deployment and usage would be entirely up to the library or hosting provider
  • Should suitably rich bulk APIs be added to the individual modules, then the necessity of this dedicated module would be reduced, and it could eventually be deprecated.

I look forward to reading the notes from today's meeting!

 

Cheers,

 

 

Ian

 

On Sun, Feb 14, 2021 at 11:07 PM Dale Arntson <arnt@uchicago.edu> wrote:

Hi all,

We will meet again on Monday, Feb. 15, at 11 EST. We have several topics we hope to discuss.

Dennis Bridges will attend to discuss changes and improvements to the APIs for organizations, orders, invoices, and finance that are needed to support data migration, and which changes should be prioritized.

Ian will be working on a POC to implement bulk APIs for data migration using a separate, dedicated module. We discussed this briefly last time, and I wanted to leave some time during this meeting to continue the discussion, if people have more to say.

Ian will be working on a POC to implement bulk APIs for data migration using a separate, dedicated module. We discussed this briefly last time, and I wanted to leave some time during this meeting to continue the discussion, if people have more to say.

Last week Marcia Borensztain came to discuss principles for producing documentation of data migration strategies and procedures. We would like to hear more from the group about what we think we could do, and  what we have time to do. Ebsco has said that it will continue to fund Marcia's position if the SIGs can dedicate someone to work on documentation for their domain. Technically, we are not a SIG, but we do work in a domain that needs to documented for institutions who want to adopt Folio and are trying to adapt it to their needs. Is there someone in our group who can dedicate a certain amount of time over the next six months to working on documentation? We will discuss more during the meeting.

Hope you will be able to make it.

Best,

-dale


Meeting link: https://zoom.us/j/204980147
Password: folio-lsp
Agenda: https://wiki.folio.org/display/SYSOPS/Copy+of+2021-02-15+-+Data+Migration+Subgroup+Agenda+and+Notes


To unsubscribe from this list please go to http://archives.simplelists.com


 

--

Ian Walls

FOLIO Implementation Lead

Phone: (888) 900-8944

pronouns: (he/him/his)

timezone: Eastern



To unsubscribe from this list please go to http://archives.simplelists.com

To unsubscribe from this list please go to http://archives.simplelists.com



--
Ian Walls
FOLIO Implementation Lead
pronouns: (he/him/his)
timezone: Eastern



To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=qG0SS9vLBzCgdZEZ6cAjLA8WupMZuam7