Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Discussed at a previous meeting on 8/6. From Christie’s understanding:
We discussed the implementation topic tracker page and its role in our process and how it supports the SIG. This page is general and high level. Anyone can add a topic to the table. Just need a brief description, your name and if there is a JIRA you can link it. Anyone can add themselves as an interested party. The table needs updating. Maybe we don’t
We discussed codifying in the JIRA what we discussed so that anyone can look at the JIRA and see that it was discussed.
Jennifer: once we discuss and create a JIRA can a topic be archived as now it will be tracked in JIRA
Christie: yes, that is a good suggestion, we need to find a way to move things off the long table but also make sure we don’t lose anything
Jeanette: Do we need a table that tracks where things have been moved to
Vivian: I still need a better understanding of how does it work for development, decision making, etc. Maybe a topic for a future meeting
Jennifer: we have the archived table and every JIRA that has been closed is there. Maybe the table needs to be renamed. We do have a page with dashboards for all the issues and dashboards where you can find everything https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/997326849
Christie: I thought the archive was for the older way and not for the issues that were resolved.
Another issue is how are we assessing if things have actually been solved. In the past things were brought up, discussed, development was done, JIRAs were closed as if the issue was solved but the issue still persists.
Jennifer: I think we need to move anything that has a JIRA off the spreadsheet as its easier to keep track of through the JIRA dashboards instead of the spreadsheet.
Christie: Would be useful for her and Jennifer to listen to these two meetings again and make the final decision on how to use these working documents. Bring back to the group well documented processes. Should help with Vivian’s questions and a better understanding for everyone and a move towards positive movement for DI.
Would be really useful to document what our vision for DI is so that we have some sort of roadmap or a community vision that is documented.
Vivian: the process for how development happens is not clear. Would be awfully nice to have a document. Especially for new people.
Christie: The DI community has struggled for a long time. This discussion is really awesome.
Jeanette: We should really talk to the Linked Data community. Everything now in DI is MARC centric and we need, as a community, to understand where we are going as so many libraries are moving away from MARC and that has not been discussed at all.
Jennifer: Excellent point, Jeanette. That was part of the original roadmap for DI. Christie raises a great point that we need to understand where we are now with DI and MARC, and then we can move forward.
Christie: if we are talking about the functionality of DI then the MARC functionality is going to be more built out than anything else. We can start talking to the Linked Data SIG. I worry about how they envision the practical implementation. There are less consistencies. There are no best practices. We need that before we talk about functionality. Maybe our goal for the year needs to be to connect with LD and discuss how we can make progress. Adoption of new technology is a process. Thank you for bringing it up, and we need to reach out to them. Maybe we should have a joint meeting with the Linked Data SIG and discuss how we could start the process. Maybe after WolfCon
Ryan: thinking about this a lot for future releases. I see us tightening up MARC issues while being in closer communication with LinkedData. Transitional time as LD gets more development. Would also like to meet after WolfCon.
Jennifer: spoke to the developers of the LinkedData app in FOLIO. We need more information on how the LD systems interact with FOLIO
Christie: Having a working group that documents the LinkedData sources and how they work with FOLIO. We need to understand the scope of expectations for all the different LD sources. Would be great if by the end of the year we had some tickets in place for this kind of work.
Back to our process and documents work. How do we document the process itself? Something that explains how we are doing the work in the SIG and how we are making progress.
Jennifer: We have a page called DI implementers topics. Just has a link to the other pages. Do we need a page that explains the different ways to contribute to DI? Where can you find the issues and what stage they are in.
Vivian: Would like a link at the top of the page with an explanation of how it all works. A list of all the topics that are being worked on and what to do if I have a new idea that needs to be developed. Who do I talk to? Like a statement of process. The current process is not intuitive.
Jeanetts: My experience is that the pathways are very different for each environment. Knowing when to write a JIRA, when to put it on the topic tracker, when to reach out to the PO, to the hosting vendor, etc.
Christie: yes, its complicated and difficult but that doesn’t mean we shouldn't try. Worth thinking about what we can and can’t do. Document what the SIG can do and how we do it. Have a process and sources for when that process is enough. Maybe not as detailed as others want but something top level.
Jennifer: We can make suggestions. If you are hosted and you see a but do this, and similar. Set up expectations of what the SIG can help you with. There are gray areas
Vivian: In some SIG I posted a problem and was told I found a bug. I reported to Ebsco as we are hosted by them. They said it wasn’t a bug and was working as expected, this was an enhancement. Now, what do I do? That is the answer I’m looking for.
Christie: That is a fair request, and I hope that our process will enable us to answer that question and follow through.
Vivian: I understand that for different institutions the answers will be different but still having some steps to follow would be super helpful. Other SIGS do things differently. I want to know what the answer to “Now what?” is
Christie: We haven’t had an answer to that question and the object of this discussion is to find an answer. Even if we don’t always know, let's get a start, develop a process, and be open to reworking it in the future if needed. Thank Vivian for articulating the issue so well.
Christie: Want to hear from everyone how you feel about today’s discussion. Along with Jennifer we will come up with some documents. Please add your ideas, comments, thoughts in the slack. Maybe we can meet in person at WolfCon
Jeanette: Do we have access to GoogleDrive?
Jennifer: Yes, but the permissions are weird. Only the conveners can create and then we share.
Christie: we can discuss if certain types of work can be created and worked on in the shared space. Let's talk about that and we can ask about broader permissions for the drive if needed
Need to update the link on our page so that it goes to the correct topic tracker page.
Christie ill reach out to Jeanette to talk about ideas on how to engage with LD. Possibly schedule a joint meeting with the Linked data SIG after WolfCon
Jennifer & Christie will create some documentation of our processes and bring back to the SIG for comments. May share in the Google Drive, depending on permissions.