<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:48:52 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INFRA-48] Add new project &quot;DB&quot;</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-48</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;Add new project &quot;DB&quot; (SPT database) for database development underway by Yasuda-san.&lt;br/&gt;
better project name (and description?) are desired.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11105">INFRA-48</key>
            <summary>Add new project &quot;DB&quot;</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</priority>
                        <status id="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Thu, 28 Jul 2016 06:12:57 +0000</created>
                <updated>Tue, 10 Jan 2017 02:24:15 +0000</updated>
                            <resolved>Tue, 10 Jan 2017 02:24:15 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="11201" author="rhl" created="Thu, 28 Jul 2016 12:54:46 +0000"  >&lt;p&gt;How about, &quot;OPDB&quot; &amp;#8211; it&apos;s the Operational Database.&lt;/p&gt;</comment>
                            <comment id="11204" author="atsushi.shimono" created="Thu, 28 Jul 2016 13:37:19 +0000"  >&lt;p&gt;good point. OPDB seems better.&lt;br/&gt;
let me get Yasuda-san here.&lt;/p&gt;</comment>
                            <comment id="11354" author="atsushi.shimono" created="Thu, 29 Sep 2016 07:11:22 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=naoki.yasuda&quot; class=&quot;user-hover&quot; rel=&quot;naoki.yasuda&quot;&gt;naoki.yasuda&lt;/a&gt; let me hear your thought.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=rhl&quot; class=&quot;user-hover&quot; rel=&quot;rhl&quot;&gt;rhl&lt;/a&gt; Although I filed as database system for survey operation currently under development by Yasuda-san, but do we better to have only one project for entire DB things (from on-site operation to survey science)? How do you think?&lt;/p&gt;</comment>
                            <comment id="11732" author="atsushi.shimono" created="Tue, 10 Jan 2017 02:24:15 +0000"  >&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;From offline discussion at collaboration meeting 2016&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Items relates on survey operation is now pointed to the SURVEY project, which contains ETC (exposure time calculator). This OPDB could be in the SURVEY project, as well.&lt;br/&gt;
For &quot;database&quot; organization point of view, science analysis operation is now separated from others, in collaboration with MSIP etc., and is handled in the DB project.&lt;/p&gt;

&lt;p&gt;So, for now, close this ticket without nothing, and guide the database for survey operation into the SURVEY project.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10006" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>INFRA-43</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii00m7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>